Difference between revisions of "List of software customizations/enhancements"
From PKP Wiki
| Line 34: | Line 34: | ||
|1 request | |1 request | ||
|? | |? | ||
| − | | | + | |JM: Would the MathJax plugin suffice? http://pkp.sfu.ca/support/forum/viewtopic.php?f=28&t=6954. Should eventually be added to main OJS package. |
|- | |- | ||
|OJS: Allow italics in title field without having to use explicit html codes that will show in the title in places you do not want them to. | |OJS: Allow italics in title field without having to use explicit html codes that will show in the title in places you do not want them to. | ||
Revision as of 11:27, 8 July 2011
| Wishlist Item | Detailed requirements | Priority | Complexity (Low, Medium, High) | Action |
| OJS: Make importing content easier | Quick Submit plugin, Expedited Submission Process, and XML importing currently exist. We'd need some detailed specifications on what a better method would look like. | 3 requests | H | |
| OJS: Massive archival entry | Simplified web interface and workflow to input metadata for backfiles. UPatras had implement a previous version not integrated to OJS. Probably need to merge issue with aforementioned (quick submit plugin) | 1 request | M | |
| OJS: Some discipline specific issues regarding reviewing and review forms that are not currently well captured in the software. | More information required | 2 requests | ? | |
| OJS: Create a third prefix field for author names, like ‘van Dongen’ or ‘de Jong’. | 1 request | L | ||
| OJS: Scientific character recognition | When uploading some content (e.g., abstract text) certain elements of the text are not always recognised, particularly related to scientific symbols. Where this has happened, I need to enter html code for the required symbol into the metadata for it to work. | 1 request | ? | JM: Would the MathJax plugin suffice? http://pkp.sfu.ca/support/forum/viewtopic.php?f=28&t=6954. Should eventually be added to main OJS package. |
| OJS: Allow italics in title field without having to use explicit html codes that will show in the title in places you do not want them to. | 1 request | ? | ||
| OJS: Most read/downloaded articles | This could be a plugin based on article views | 2 request | M | |
| OJS: Option to link complete issue PDF | This could be added to the Issue Data page as an upload box. | 1 request | M | already in the development release |
| OJS: Rapid publishing | Quick Submit plugin or Expedited Submission process should meet this need. | 1 request | L | |
| OJS: More detailed help during author submission | Detailed text would be required. | 1 request | M | |
| OJS: Regional workshops | 1 request | Perhaps PKPEN could sponsor a quarterly series of webinars and/or regional workshops. | ||
| OJS: Transform OJS into a full blown repository | More information required | 1 request | H | Detailed functional specifications and funding source required. |
| OJS: more personalization e.g. comments and additional exporting options | Capability to include article comments, capability for additional exporting options | 1 request -low priority | ? | |
| OJS: authorities (for authors) | Need for authors authorities initially may be organisations later. Autocompletion function based on previous entries. Need when journals expand. No need for central authority interface only locally | 2 requests | ? M ? | |
| OJS: Article page by page/"e-book" view | Present article as a e-book with open source ebook reader in a page by page/thumbnail/etc view. Similar to IA book reader (example http://www.archive.org/stream/worksofrogerspee01roge#page/n1/mode/2up http://reader.ekt.gr/bookReader/show/index.php?lib=GRSER&path=GRSER_00000000000003053_#page/42/mode/thumb) Have to be implemented by interfacing to an external system | 1 request | Medium- High | |
| OJS: Dynamic Article cover page generation | Automatically create article cover page based on metadata and a pdf template. In beta internal version from EKT | 1 request | Low | |
| OJS: Possibility to display the article views to the reader | 1 request | |||
| OJS: Possibility to define new roles and workflow steps | 3 request | H | ||
| OJS: Management of article versions | 1 request | H | ||
| OJS: Consider translation step and role in the workflow. | 1 request | ? | ||
| OJS: More flexible horizontall navigation. | 3 request | ? | ||
| OJS: Define workflow steps for each article. | 1 request | ? | ||
| OJS: The role of a guest editor, that will just be able to read/preview an unpublished issue. | 1 request | ? | ||
| OJS: Automaticaly extract metadata from the uploaded submission. | 1 request | ? | ||
| OJS: Modern, AJAX based design. | 1 request | ? | ||
OJS: Possibility to use different classifications, e.g.:
|
1 request | ? | ||
| OCS: Integrate OCS payment system into a membership structure - we would like to have a one-stop shop for membership of our organisation and special rates for our conferences | 1 request | H | ||
| OCS: Want to migrate from one OCS conference to another. | Existing XML Import/Export tools should meet this need. Need details on how this is insufficient and what should be added/enhanced. | 1 request. | ? | |
| OCS: Participant list | Automatically create a participant list. Visible on the OCS site from a given date (like registration etc.) with some flexibility (choices) regarding which information will be visible. | 1 request | medium? |
