Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Journal Managers to Invite users to adopt a role - Reviewers #9659

Open
Devika008 opened this issue Jan 27, 2024 · 0 comments
Open

Allow Journal Managers to Invite users to adopt a role - Reviewers #9659

Devika008 opened this issue Jan 27, 2024 · 0 comments
Assignees
Labels
Community:2:Priority Any issue that has been identified through research or feedback as a major community priority. Enhancement:2:Moderate A new feature or improvement that can be implemented in less than 4 weeks. Privacy Any issue that impacts user privacy, such as GDPR and other privacy regulations.
Milestone

Comments

@Devika008
Copy link

Devika008 commented Jan 27, 2024

Hello,

Since #3022 (comment) was too big, upon discussion we decided to divide it into four smaller issues.

This second issue highlights the user flow of journal managers inviting reviewers OJS. The user flow reflects all the research, discussions and feedback received on this issue over the last few years along with some minor testing with a small user group at the Copenhagen Sprint.

Summary of the requirement

Reviewer can be added to OJS in two ways

  1. Through the review section of the submission: Here the Journal Manager (JM henceforth) / Editor can click on “Add a reviewer” action and will see the following: Reviewers already associated with the Journal and added to OJS and send a review request to them, “Add a new user”- here the JM/Editor can invite a user via email to not only review the submission but also be an OJS user in reviewer capacity- and “Enroll an existing user” - here the JM/Editor can add the reviewer role to a user who already has other OJS roles along with sending an invitation to review the submission.
  2. Through the “Users & Roles” section: Here the JM/Editor can either add a new user to OJS as a reviewer or add a reviewer role to an existing OJS user. The user will then be shown in the existing reviewer section of “Add a reviewer” on a submission.

Here, I am showing the workflow of editor inviting the reviewer from the reviewer panel in the workflow

Image

Image

A. The reviewer does not have an existing user account. And the JM/Editor want to invite the reviewer through the reviewer panel in the submission

  1. Image

  2. Image

  3. Image

  4. Image

  5. Image

  6. Image

  7. Image

  8. Image

  9. Image

  10. Image

  11. Image

Alternative order of steps a potential reviewer can undertake. Here the reviewer reads about the submission before creating an account in OJS

  1. Image

  2. Image

B. Enrol Existing User who is ORCiD Verified

  1. Image

  2. Image

  3. Image

  4. Image

  5. Image

  6. Image

  7. Image

C. Enrol Existing User who is not ORCiD Verified

  1. Image

  2. Image

  3. Image

  4. Image

  5. Image

  6. Image

  7. Image

  8. Image

D. Existing Reviewer who are not ORCiD verified

  1. Image

  2. Image

  3. Image

  4. Image

  5. Image

  6. Image

  7. Image

  8. Image

E. Existing Reviewer who is ORCiD verified

  1. Image

  2. Image

  3. Image

  4. Image

  5. Image

  6. Image

@Devika008 Devika008 converted this from a draft issue Jan 27, 2024
@Devika008 Devika008 added Community:2:Priority Any issue that has been identified through research or feedback as a major community priority. Enhancement:2:Moderate A new feature or improvement that can be implemented in less than 4 weeks. Privacy Any issue that impacts user privacy, such as GDPR and other privacy regulations. labels Jan 27, 2024
@Devika008 Devika008 added this to the 3.5.0 LTS milestone Jan 27, 2024
@asmecher asmecher modified the milestones: 3.5.0 LTS, 3.6 Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community:2:Priority Any issue that has been identified through research or feedback as a major community priority. Enhancement:2:Moderate A new feature or improvement that can be implemented in less than 4 weeks. Privacy Any issue that impacts user privacy, such as GDPR and other privacy regulations.
Projects
Status: In Progress
Development

No branches or pull requests

6 participants