-
Notifications
You must be signed in to change notification settings - Fork 452
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
Redesigned Dashboard - Review Assignment Views #10970
Milestone
Comments
jardakotesovec
added a commit
to jardakotesovec/ui-library
that referenced
this issue
Feb 25, 2025
…d and moved to copyediting&production stage (covered in pkp/pkp-lib#10970)
jardakotesovec
added a commit
to jardakotesovec/ui-library
that referenced
this issue
Feb 25, 2025
…d and moved to copyediting&production stage (covered in pkp/pkp-lib#10970)
jardakotesovec
added a commit
to pkp/ui-library
that referenced
this issue
Feb 25, 2025
…d and moved to copyediting&production stage (covered in pkp/pkp-lib#10970)
Vitaliy-1
added a commit
to Vitaliy-1/pkp-lib
that referenced
this issue
Feb 26, 2025
PR pkp-lib: #10989 |
Vitaliy-1
added a commit
that referenced
this issue
Feb 26, 2025
#10970 Implement reviewer views according to new logic
Merged but requires testing, not closing for now |
jardakotesovec
added a commit
to jardakotesovec/pkp-lib
that referenced
this issue
Feb 26, 2025
jardakotesovec
added a commit
to jardakotesovec/pkp-lib
that referenced
this issue
Feb 26, 2025
jardakotesovec
added a commit
that referenced
this issue
Feb 26, 2025
jardakotesovec
added a commit
that referenced
this issue
Feb 26, 2025
jardakotesovec
added a commit
to pkp/ui-library
that referenced
this issue
Feb 26, 2025
ipula
pushed a commit
to ipula/ui-library
that referenced
this issue
Feb 27, 2025
Vitaliy-1
added a commit
to Vitaliy-1/pkp-lib
that referenced
this issue
Feb 27, 2025
…published submissions
PR: #10997 |
Vitaliy-1
added a commit
to Vitaliy-1/pkp-lib
that referenced
this issue
Feb 27, 2025
Vitaliy-1
added a commit
that referenced
this issue
Feb 27, 2025
#10970 show completed reviews in all assignments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue: Reviewer Dashboard Views and Submission Statuses
Description
This ticket outlines the different dashboard views a reviewer sees and the submissions that appear in each view based on their status. The goal is to ensure that submissions are correctly categorized and that reviewers can take the appropriate actions at each stage.
Dashboard Views & Submission Statuses
1️⃣ Dashboard View: Action Required by Me
Submissions appear here when immediate action is required by the reviewer.
2️⃣ Dashboard View: Completed
Submissions appear here when the review process has been completed or the submission has progressed to the next stage.
3️⃣ Dashboard View: All Assignments
This view includes all submissions assigned to the reviewer or actively managed by the editor or reviewer, excluding declined, published, or archived submissions, as no further action is required for them.
Even after moving to copyediting or production, the reviewer remains associated since they submitted the review, and the editor can bring it back to review if needed. However, if the reviewer declined the request, the submission was published, or the review was left incomplete, the reviewer can no longer take any action.
4️⃣ Dashboard View: Published
Submissions appear here when a reviewed submission has been published.
5️⃣ Dashboard View: Archived
Submissions appear here when the review is incomplete, but the submission has already moved forward. (complete submission is considered in context of this ticket as review which is submitted, regardless whether it was confirmed)
6️⃣ Dashboard View: Declined
Submissions appear here when a reviewer declines the review request, regardless of the submission’s final status.
🔹 Note: The submission remains in this view even if it is later published.
More Edge Cases
These edge cases apply to incomplete reviews, where the submission will not be moved to the Archived view for the reviewer:
a. The review is incomplete, but a new review round is created.
b. The review is incomplete, but the submission advances to the next review stage (OMP).
c. The review is incomplete, and the submission is moved back from copyediting to review.
🛠 Other Considerations for Development
1️⃣ Handling Multiple Review Rounds
2️⃣ Ensuring Correct Transitions Between Views
The text was updated successfully, but these errors were encountered: