Open NateWr opened 5 years ago
NateWr
commented
3 years ago During a review of other platforms, @israelcefrin noted that Janeway visually distinguishes between incomplete and complete submissions in the author dashboard. This is a distinction we should also make clear when we separate author assignments from editorial assignments.
NateWr
commented
2 years ago The following mockups have been prepared as a suggestion for how these lists can be split up, and what the new author and reviewer lists should look like. Changes to the submissions list will be handled in a separate issue.
When a user has more than one role, they will see a menu item for each page.
They will only see the menu items appropriate for their role:
ROLE_ID_MANAGER, ROLE_ID_SUB_EDITOR or ROLE_ID_ASSISTANT role (eg - Journal Manager, Section/Series Editor, Moderator, Copyeditor, Layout Editor, etc.)ROLE_ID_REVIEWER role.ROLE_ID_AUTHOR role (eg - Author, Translator)The My Submissions page shows the author a simplified list of submissions.
The Review Assignmentss page shows the reviewer a list with the appropriate information shown/hidden.
Once a review assignment is completed, declined, or cancelled by the editor, it is moved to the reviewer's archived list.
Devika008
commented
8 months ago Based on the designs for the submission lists, here is my proposal on how editor, author and reviewer assignment can look like
For editor in the dashboard, their review and author assignments are placed in the main menu
Author Dashboard
Reviewer Dashboard
Devika008
commented
3 weeks ago This has already been incorporated and worked on as a part of the New Submission Dashboard :D
Describe the problem you would like to solve Editors, authors and reviewers who have more than one role in the system struggle to identify which submissions they have to review, edit or follow-up on. This is especially difficult for editors who handle more than one role.
Describe the solution you'd like Separate out editorial, review and author assignments into separate submissions lists.
Who is asking for this feature? Editors who were also reviewers and authors.
Additional information The UI/UX group at the Pittsburgh Sprint in 2019 suggested that these submissions should appear in separate lists.
The API endpoint for submissions has a lot of conditional logic to determine the user's currently assigned role. This is used, for example, to anonymize data about the submission for reviewers. Because the API endpoint returns editorial, review and author assignments, the logic has to sit deeply inside the submissions schema map and other places. Once there are separate API endpoints for editorial, review and author assignments, this logic can be removed, which will simplify the schema map and the API endpoints.