Difference between revisions of "OJS Roadmap"

From PKP Wiki
Jump to: navigation, search
Line 1: Line 1:
 
=Development Roadmap=
 
=Development Roadmap=
  
==Milestone 3.0 ('''Current - Q4 2009''')==
+
You will find the OJS development roadmap for 2009 below. Please note that these dates are not fixed. OJS development is currently following two development branches: a 'stable' 2.2.x line which includes mainly bugfixes and will be an easy upgrade for users of the current 2.2.2 release (and who do not need much in the way of new features); and a 'devel' 2.3 line, which includes large-scale changes in the underlying codebase as well as many new features.
  
'''<big>PKP Framework</big>'''
+
While we do attempt to list all bugs tracked against a given release, quite often a bug report against one release will be ported to another (this is especially the case with 2.2.x bugfixes into the devel branch; less so with 2.3 enhancements into the stable branch). This is also the case with some bugs tracked against other applications such as Open Conference Systems. You are encouraged to browse [http://pkp.sfu.ca/bugzilla our Bugzilla database] fully.  
* Development of a common framework for all PKP software.
+
* See [http://pkp.sfu.ca/node/1600 Modularization of PKP Systems] for details.
+
  
==Milestone 2.3 ('''Current - Q4 2008''')==
+
== Milestone 2.2.3 ('''Q1 2009''') ==  
  
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3286#c0 Article of the day]
+
This is a planned stability/bugfix release of the 2.2.x line, roughly scheduled for April 2009. Very few new features will be included with this release.  
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3543#c0 Photos for Masthead]
+
* [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Open+Journal+Systems&version=2.2.3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= All bug reports].
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3701#c0 Allow for short Announcements]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=1677#c0 Package OJS as CVS checkout]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=1709#c0 For users who will not be using OJS to publish journal co...]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=1848#c0 W3C Validator complaints]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=1856#c0 Disable user creation/enrollment for disabled roles]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=1860#c0 Streamline access for users with a single role]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=2052#c0 example wording of path]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=2954#c0 Import Timeout Issues]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3118#c0 Report a Bug/Request a Feature for Users]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3225#c0 Include word counts for locale keys and files]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3255#c0 Multiple thesis authors]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3284#c0 Tag-cloud of submission keywords]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3285#c0 List most searched-for words]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3487#c0 Add RSS feed for article comments]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3619#c0 Access to printer-friendly version of article if RT disabled]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3647#c0 Register existing using button does not validate role]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3652#c0 Merge users should selectively transfer subscription]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3683#c0 Add TinyMCE support to reviewer comments]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3687#c0 Extend the xmlGalleys plugin to include support for DocBo...]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3698#c0 Reply to reviewer comments should quote parent title + 'Re:']
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3700#c0 Allow for image uploads with TinyMCE]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3712#c0 Custom Sidebar Block Plugin]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3718#c0 Extend Editor/Author review workflow to include multiple ...]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3728#c0 Expedited Submission Process creates unecessary copies of...]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3747#c0 Italics in titles causing issues with reading tools display.]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3748#c0 Advanced search year is hardcoded in, insufficient for ol...]
+
* [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3750#c0 moving common templates into the PKP source tree and abst...]
+
  
 +
==Milestone 2.3 ('''Q2 2009''')==
  
 +
OJS 2.3 is a substantial upgrade from the 2.2.x line, including many new enhancements as well as all relevant bug fixes against 2.2.x., and is loosely scheduled for release around June 2009. This will be the first OJS release that will make use of the new abstracted PKP WAL common codebase. The User Interface will remain largely the same as the 2.2.x line. You can view all bug reports by type:
  
==Proposed for Future Release==
+
* [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Open+Journal+Systems&version=2.3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= All bug reports]
 +
* [http://pkp.sfu.ca/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Open+Journal+Systems&version=2.3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&bug_severity=trivial&bug_severity=enhancement&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Feature requests/enhancements]
  
===Less linear workflow===
+
==Milestone 3.0 ('''Q4 2009''')==
* 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===
+
This proposed release will represent a large-scale revamping of the PKP codebase, including the completion of abstracting common code from all applications into the PKP WAL; modularization of the remaining OJS codebase (so that components can be mixed and matched as necessary); substantial and comprehensive User Interface refinements; and further overall code refinements. The release date is largely hypothetical at this point, and no bugs have yet been filed against 3.0.
* "In press" section for articles that are currently in holding for actual publication.
+
  
===Thesis Workflow Tool===
+
* See [http://pkp.sfu.ca/node/1600 Modularization of PKP Systems] for details on the proposed modularization of PKP applications.
* 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===
+
* 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===
+
* configurable metadata: mappings to/from common schemas? (eg. DC, METS)
+
* output in multiple document formats (galleys framework refactor)
+
* Shibboleth, CAS, WebAuth, SiteMinder, OpenID
+
* APT/Ubuntu package installation
+
* lucene-compatible full-text indexing
+
* EPrints uses LCSH controlled vocab. indexing + local structure
+
* expose all data as RDF (Hyperjournal)
+
* SQLite storage backend (through ADODB; speaking of which, an update to bundled ADODB version?)
+
* custom role permissions
+
* fully customizable workflow
+
* direct submission ingestion via, eg. FTP or WebDAV
+
* "the same article can belong to multiple journals" (TOPAZ)
+
* "contextualization" features for linked bib data (this seemed like OJS' reading tools?) (Hyperjournal)
+
* add option to "display ISSN in sidebar" near the ISSN field in journal setup
+
* 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.
+
* announcements should display newest to oldest by default; and also allow for re-ordering by the JM
+
* 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.
+
* Add a "email reviewer" icon to the editor interface for each submission. This would allow communication between the reviewer and the editor to take place within OJS and be captured in the History
+
* 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).
+
* Make the CSS and/or templates editable within the web admin interface -- see WordPress as an example
+
* Enabling specific reading tools at a section level - Submitted by Mark Weiler (mweiler@sfu.ca) - Currently, when reading tools are enabled, they are enabled for all the issues (current, future, past) in the entire journal. Thus, the decision to enable reading tools is global (affecting all sections) and is diachronical (affecting all past/present/future) issues. It would be useful feature if the journal manager or editor could create sections and specify what reading tools are enabled for those particular sections and even particular issues. With respects to the reader comments reading tool, this would allow editors to create innovative sections. For example, a journal may want to have a section that is unique in that editorial team actively seeks readers to add comments to the articles. Or a journal that is in the practice of enabling readers to comment for all sections, may wish to create a section that does not have reader comments enabled.
+

Revision as of 13:43, 14 February 2009

Development Roadmap

You will find the OJS development roadmap for 2009 below. Please note that these dates are not fixed. OJS development is currently following two development branches: a 'stable' 2.2.x line which includes mainly bugfixes and will be an easy upgrade for users of the current 2.2.2 release (and who do not need much in the way of new features); and a 'devel' 2.3 line, which includes large-scale changes in the underlying codebase as well as many new features.

While we do attempt to list all bugs tracked against a given release, quite often a bug report against one release will be ported to another (this is especially the case with 2.2.x bugfixes into the devel branch; less so with 2.3 enhancements into the stable branch). This is also the case with some bugs tracked against other applications such as Open Conference Systems. You are encouraged to browse our Bugzilla database fully.

Milestone 2.2.3 (Q1 2009)

This is a planned stability/bugfix release of the 2.2.x line, roughly scheduled for April 2009. Very few new features will be included with this release.

Milestone 2.3 (Q2 2009)

OJS 2.3 is a substantial upgrade from the 2.2.x line, including many new enhancements as well as all relevant bug fixes against 2.2.x., and is loosely scheduled for release around June 2009. This will be the first OJS release that will make use of the new abstracted PKP WAL common codebase. The User Interface will remain largely the same as the 2.2.x line. You can view all bug reports by type:

Milestone 3.0 (Q4 2009)

This proposed release will represent a large-scale revamping of the PKP codebase, including the completion of abstracting common code from all applications into the PKP WAL; modularization of the remaining OJS codebase (so that components can be mixed and matched as necessary); substantial and comprehensive User Interface refinements; and further overall code refinements. The release date is largely hypothetical at this point, and no bugs have yet been filed against 3.0.