OJS Roadmap

From PKP Wiki
Revision as of 09:12, 4 March 2008 by Admin (Talk | contribs)

Jump to: navigation, search
OJS Roadmap
Future directions for OJS
Less linear workflow
Status: TBA
Less downloading and uploading req'd for workflow
Possibility of using a single file for all workflow and tracking changes rather than submitting new files for each stage (perhaps with drag and drop, with copies left behind for documentation)
Better support for pre-prints
Status: TBA
"In press" section for articles that are currently in holding for actual publication.
Thesis Workflow Tool
Status: TBA
OJS as a thesis submission and tracking system.
SFU Library has a project on the books to develop a more robust thesis workflow tool.
Submission as single file
Status: TBA
Submission model might be made better by including the option to make a .pdf containing the article, all supplementary files and appropriate metadata. Advantages include no need to de-identify properties, and review document is a single document - no need to download all figures, supplementary documents, etc in order to review. Of course, letter to editor and other documents not for reviewers would need to be submitted not to be included.
Status: TBA
add 'Former Journal Title' and 'Former ISSN' as repeatable fields, for journals that have changed their names and/or ISSNs once or twice or more.
import transaction/rollback
more flexible statistics
arbitrary metadata gateway
Dspace export
support alternate stylesheet for PDA viewing
support for embedded video (youtube style)
user/article thesaurus/controlled vocabulary
user tagging
ACL:based permission classes
WYSIWYG special character handling (e.g., tinyMCE extension for latek)
"login as" behavior should be limited in certain contexts
centralized role management for plugins
featured article plugin/block
user friendly error handling/logging
local private messaging system a la phpBB
scholar's portal plugin interface (UTL)
advanced search options / interfaces (eg. zend lucene index plugin)
mobile / WML plugin (athabasca)
exporting to LAC web interface
option to make abstracts a required field for journal sections
add DOI to citations
"Advice Tool" - integrating links to publishing references directly into the interface (or in the Help files). - from Mark Weiler, email Nov 6, 2007
Allow reviewers to make additional comments after completing their review.
Allow Journal Managers to create customized email groups for sending out messages (i.e., they could create an email 'group', select the users to include, and then send to that group whenever required).