OJS development discussion, enhancement requests, third-party patches and plug-ins.
Moderators: jmacgreg, btbell, michael, bdgregg, barbarah, asmecher
The OJS Technical Reference
and the OJS API Reference
are both available from the OJS Documentation
You can access our public Git Repository here
. Comprehensive Git usage instructions are available on the wiki
You can access our Bugzilla report tracker here
You can use our Google Custom Search
to search across our main website, the support forum, and Bugzilla.
Questions and discussion are welcome, but if you have a workflow or usability question you should probably post to the OJS Editorial Support and Discussion
subforum; if you have a technical support question, try the OJS Technical Support
Our idea is must likely impossible, but I thought that I should ask anyway. Sometimes an informed “no” is better than to have a loose suggestion in back of your head.
When we give courses to new journals they often ask if they could have changes to the editorial workflow. Often we need to say no because the demands of the editorial boards would require recoding the server….
But we discussed if it would be possible to divide the editorial process a bit more op and make it into individual “blocks”, where you s an minimum can choose NOT to include a given section. As an example to choose NOT to use the sections regarding layout and ensure that the editors can not even see that the sections are there.
- Posts: 9
- Joined: Fri Oct 15, 2010 1:15 am
Thanks -- that's good feedback and not the first time we've heard it. We're talking usability -- again for OJS 3.0 -- and hopefully will have time to consider some of these ideas for that release. If not, they'll be high priority for the follow-up.
Public Knowledge Project Team
- Posts: 10015
- Joined: Wed Aug 10, 2005 12:56 pm
Return to OJS Development
Who is online
Users browsing this forum: Google [Bot] and 1 guest