jardakotesovec
commented
3 months ago @Vitaliy-1 Just to summarise what @Devika008 is proposing to display to authors.
- In general it just displays how many reviews are completed / are active, which is same as current system.
- When the reviews are open, she would like to also displays reviewer name & initials for these. We can put Initials aside, we will figure out where to calculate them in separate issue. But basically need reviewMethod and reviewer name.
If we would want to include just the minimal info (counts, and open reviewers names) that would be fine. If we share full reviewAssignments with statusId - thats fine as well - its easy to calculate the counts client side. Obviously we need to include names only for the open reviews situation.
Not sure whether sharing any other fields would be problematic. Also whether sharing declined/cancelled review assignment might not be desirable?
Would need these both for _submission and /submission/{submissionId}/
Vitaliy-1
Consider what submission schema data should be exposed to the author, i.e., through the API the data can be received with
.../submissions/{submissionId}endpoint.Review assignments data that is already available: id, isCurrentUserAssigned, statusId, status, due, responseDue, round, roundId. The work on submission lists adds: dateConfirmed, dateCompleted, dateAssigned, recommendation, dateCancelled.
The new data also includes: recommendationsIn, reviewersNotAssigned, revisionsRequested, revisionsSubmitted, scheduledIn.