OJS Roadmap

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.

Miscellaneous: Status: TBA; import transaction/rollback; more flexible statistics; arbitrary metadata gateway; Dspace export; 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