I try to to configure OJS3 for our review process, where. Editors-in-chief assign section editors assign reviewers, but section editors only recommend a decision to the editors-in-chief. I thus want to hide the [Send to Copyediting] Button from the SE’s review page. Ideally it is replaced by something like [Recommend Accept].
Unfortunately, the documentation only mentions the existence of permission levels, but does not exlain the different possibilities. How can I configure what I described above? If impossible, how can I work around?
OJS doesn’t yet support a process where section editors recommend a decision to editors, but aren’t able to actually enact a decision themselves. It’s something that’s been requested, though, so it’s likely to be added to a future release.
Regards,
Alec Smecher
Public Knowledge Project Team
Thanks for your reply. The documentation on permission levels would still be interesting. Perhaps we can model sufficient behaviour with the existing rights management.
If you can provide some raw information on the levels, I will extend the documentation.
Have you had a look at the OJS 3.0 User Guide? It has some basic documentation of the Roles setup area, but could probably stand to be expanded. Tagging @stranack, who wrote that documentation, and who also heads up a documentation working group.
Regards,
Alec Smecher
Public Knowledge Project Team
Hello Alec, I now this is an old thread, but has anything changed since last November regarding sub-editor permissions? I find 2 issues which are a bit concerning:
a sub-editor can assign other sub-editors: this should not be possible
a sub-editor without the permissions to notify authors can still send the author notification email: this should not occur, right?
Other sub-editor roles are participants in a submission right from the submission step, even though we do not want them involved. However, unless an editor has the “submission” step flagged it cannot be assigned to a submission before peer review.
I am not sure if I am busting in on you on this, but if possible I would like to strengthen the sub-editor process. Or am I the only user with this problems (which is a possibility…)
Thanks,
Lucia
Are you sure this isn’t a user that has more than just a Section Editor (a.k.a. Sub Editor) role? I’m thinking e.g. Journal Editor, Journal Manager, or Administrator roles.
Regards,
Alec Smecher
Public Knowledge Project Team
Hello Alec, thanks for your reply.
I have double checked and regarding point 1) sub-editor can assign other sub-editors this is the subject editor = permission level: section editor. Maybe a should create a new role with a different permission level?
Regarding point 2) it works ok now… possibly I needed a brand new submission to test this feature.
Regarding point 3) I have a journal manager, whom I would like to involve at acceptance but not list in the participants at submission. I tested creating a new role (permission level = assistant where I did not select the stage “submission”) but this results in this role not appearing in the “assign participant” area. Maybe this it the way it works and cannot be changed but I would like to be sure I am not simply unfamiliar.