Hi,
In 3.1.1.x the filter option is very good and helpful. The filter “overdue” now shows all articles with status message “a review is overdue”. But this could be either the “response due date” or the “review due date”. Could these two cases be better distinguished in the title overview list?
Thanks
1 Like
I’ve suggested this at the issue tracker:
opened 10:19AM - 22 Oct 18 UTC
Major Feature
Community Priority
Sponsored Development
**Describe the problem you would like to solve**
As an editor
I want to get a … rough sense of a submission's progress through peer review _at-a-glance_
so that I can more easily manage and track a large number of submissions, and compare their progress quickly.
**Describe the solution you'd like**
Include detailed information about the review assignments in the submission list. This should include the days remaining until the due date, whether the review has been completed or not, and the ability to fetch more details about each review without leaving the page.
See screenshots below.
**Who is asking for this feature?**
This has been identified as a major priority for editors in focus groups, UX research, and partner feedback.
**Additional information**
The following mockups suggest how this information could be added to the submission lists in order to give an overall view of progress as well as quick access to more detailed information.
An overview of reviews would give quick information about the review stage.
- Review / 1 = submission is in round one of review
- 72 days ago = submission entered the round of review 72 days ago
For each review assignment, a circle will appear to indicate the deadlines and incomplete/complete status.
- Green = complete
- Red = overdue
- Red outline = recently overdue
- Orange outline = will be overdue soon
- Blue outline = waiting for the reviewer to accept or complete the review
To help editors understand and learn the indicators, each circle can be clicked on to learn more about the review.
This issue description has been rewritten to reflect proposed changes for 3.5. The original issue description is below.
> This issue builds on UI/UX feedback and discussions in https://github.com/pkp/pkp-lib/issues/4103 and https://github.com/pkp/pkp-lib/issues/1662, which highlight the desire for more fine-grained status reporting from the submissions list.
>
> Most of this feedback focuses on the Review stage and it is the stage with the fewest technical obstacles to providing more fine-grained status. Within the review stage we have the following indicators we can use to signal progress:
>
> - How many reviewers are assigned in the current round
> - How many reviewers have accepted/declined in the current round
> - How many reviewers have completed their review in the current round
> - Has a request revisions editorial decision been made since the current round was initiaited
> - Have revisions been submitted since the last editorial decision was made
> - How many review rounds have been initiated
> - How many days a submission has been in a review round or the whole review stage
>
> Figuring out how best to represent progress will require some experimentation. We discussed the possibility of using a progress bar, which would give a very quick comparison but lacks detail about why a particular progress level is calculated. This could maybe be compensated with information it the dropdown display. A dot-system has been proposed at https://github.com/pkp/pkp-lib/issues/4103 with the caveat that interpretation of the dots be difficult without specific training.
>
> I have assigned this to the 3.2 milestone because it was considered a high priority for UI/UX improvements. However, because that milestone is already overloaded this shouldn't be taken as a promise that it will make the deadline.
1 Like