Vitaliy-1
commented
3 years ago The point is right now the "convert to JATS" is shown in very early stages and in some journals you would like to prevent authors doing this conversion during "submission stage"...
Thanks. Forgot to remove the convert button for authors on the front-end (although they didn't have permissions).
In the current master branch, permissions are granted for users with manager, editor, or assistant role starting from copyediting stage. I think in the copyediting stage editors may already want to make changes in Texture or other JATS editor, thus convert a file to JATS XML.
So IMHO, a perfect solution is a permissions-matrix with roles (y-axis) and stages (x-axis) with checkboxes, that will let the journal manager decide in what phases and what roles will see the link.
There is no easy way of doing so right now, maybe better would be to implement the generic code in OJS core that any plugin can use or consider to set custom permissions for a whole XML Workflow rather than a single plugin; not sure.
This is a feature request (or a wish) to be taken in consideration for the stable version.
The point is right now the "convert to JATS" is shown in very early stages and in some journals you would like to prevent authors doing this conversion during "submission stage"... or you would like to avoid your editors doing the conversion till the "production stage".
So IMHO, a perfect solution is a permissions-matrix with roles (y-axis) and stages (x-axis) with checkboxes, that will let the journal manager decide in what phases and what roles will see the link.
A minimal implementation (that will be enough for most the scenarios) is ignoring the roles proposal and just add 4 checkboxes in a row (one for each stage), to decide when the link will be shown.
Thanks for your work Vitaliy, m.