make any kind of download & upload at copyediting stage, & send to production stage
make any kind of download & upload at production stage & schedule for publishing
generate new issues, add submissions to those issues, than publish them,
But have not been entitled to;
make any change on Journal settings
make any change on Website settings,
and any other changes on Workflow & distribution settings.
If I am right;
It would be very handy for the journals when they enter into agreement with publishing companies, but I think there is no such a unified “Publisher’s Employee” role. But, may be the developers discuss about it for the future releases.
Regards,
Absolutely sir, you understood my suggestion. Sir this role “Publisher’s Employee” will be very beneficial for OJS Journals Publishers. Most of us publishers are not very friendly with website related softwares or we are busy with other publication related activities. An employee’s can cheat us at any time and may become owner of the journal.
Therefor I humbly request you to please discuss this suggestion with priority.
Thank for you swift reply
Regards
What would be the difference between this new role and a Journal Manager?
I think you need a user role that can;
make submissions
accept the submissions
make any kind of download & upload at copyediting stage, & send to production stage
make any kind of download & upload at production stage & schedule for publishing
generate new issues, add submissions to those issues, than publish them,
But have not been entitled to;
make any change on Journal settings
make any change on Website settings,
and any other changes on Workflow & distribution settings.
If I am right;
It would be very handy for the journals when they enter into agreement with publishing companies, but I think there is no such a unified “Publisher’s Employee” role. But, may be the developers discuss about it for the future releases.
From my previous experience, I can say that a Journal Manager has the highest privileges. In many installations, if the editor has not been registered on other journals (of the same OJS installation), he can even log in as editor, and can do any actions. It can change any journal settings too.
But, the publishing companies or the editors that enter into a publishing agreement (like me) require the staff to have no right to change any system or journal settings.
I think, such a role (or roles) may contribute to a wider use of OJS by publishing companies,
Best regards,
I think it is already possible to create such role from OJS Dashboard. You just need set it to the Section Editor Permission level.
Then you can set the Role name as wished and you can even select a few more options and grant privileges to the user.
Please, let me know whether this can be an option for what you are looking for.
Perfect, thanks for testing it.
I will add a tag for “Feature Request” to this thread and this way our dev team can track it if it is feasible to achieve on future releases.
Yes, sir, we are waiting for a new role that can make a submission to publication, but,.no right to change any system or journal settings.
This will also disallow any employee to misconduct, presently they can place their own Bank Account instead of the organisation account, etc.
Gentle reminder regarding my request of a New Role that can;
make submissions
accept the submissions
make any kind of download & upload at copyediting stage, & send to the production stage
make any kind of download & upload at production stage & schedule for publishing
generate new issues, add submissions to those issues, than publish them,
But have not been entitled to;
make any change on Journal settings
make any change on Website settings,
and any other changes on Workflow & distribution settings.
If I am right;
It would be very handy for the journals when they enter into agreement with publishing companies, but I think there is no such a unified “Publisher’s Employee” role. But, may be the developers discuss about it for the future releases."
@IJELLH, I appreciate that this is important to you, but please don’t keep posting the same request repeatedly; it doesn’t add value to the forum and doesn’t affect how we set our development priorities.
Our roadmap is public (Roadmap - Google Sheets) and if an issue hasn’t been scheduled for a future release it likely means we don’t have the capacity to prioritize it yet. We are always open to code contributions if you code or have access to development resources.
Regards,
Alec Smecher
Public Knowledge Project Team
