In OJS, a reviewer cannot access his/her recommendations from a previous round.

[pilasou]

As a reviewer reinvited to a new review round, I would like to be able the see the evaluation I provided in previous rounds.

In OJS, reviewers that are being invited to different review rounds on the same submission cannot access what was their previous recmmandations.

This improvement will offer the opportunity to reviewers to access their previous review reports and thus, better determine how the author made his/her changes to the manuscript.

The reviewer will be able to access his/her Previous round reports by clicking on a Round button on top of the reviewer process page (as shown below).

When clicking on a cycle button a new window open containing the following information:

• Recommandation
• Forms informations
• Review file sent
• Cycle dates
• Article version reviewed during preceding round

PRs:

Update (2024-04-02)
pkp/ui-library#313 (jardakotesovec repository)
pkp/pkp-lib#9526
pkp/ojs#4148

Initial:
#9526

OMP adaptation PRs:
OJS: pkp/ojs#4258
OMP: pkp/omp#1556
OPS: pkp/ops#668 TESTS ONLY

PKP-LIB: #9920 Initial Commits for PKP-LIB included

How to test?

1. Make a submission and send it to the Review step.
2. Invite one reviewer.
3. Connect as reviewer and complete the review (fill the form and add a file).
4. As editor, Request revision and select Revisions will be subject to a new round of peer reviews.
5. As an author, submit revision.
6. As editor, open a 2nd round of review.
7. Invite the 1st round reviewer.
8. Connect as the reviewer.
9. On top of the review page, you should see the Round 1 bouton.
10. In the new window, the reviewer can access its answers (forms and files).

[asmecher]

PR: #9526

@Vitaliy-1, could you review this? Thanks!

[Vitaliy-1]

Thanks, @nibou230! I left a couple of comments.

[pilasou]

Hi, @Vitaliy-1, just to let you know, I am a colleage of @nibou230, he will be on vacation for the next few weeks. Back in January. We will follow up when he comes back. Thanks!

[jardakotesovec]

@nibou230 Hi, thanks for the contribution, its certainly useful feature. Only drawback is that this is built on legacy stack and we aim to avoid adding new functionality on this old stack, because that means that we would need to migrate it to newer stack at some point anyway.

I would like to ask whether you would have some dev capacity & interest to build this feature on newer stack?

It would be creating frontend part in Vue.js (significant portion of OJS is already on Vue.js) and creating relevant API endpoints that the frontend would use.

If so, we would provide support and guidance how to do it.
In particular
frontend part: @jardakotesovec
api: @defstat
UI/UX: @Devika008

Let us know what you think

Thank you!

Jarda

[nibou230]

Hi @jardakotesovec, if our planning let me some spare time, I will do my best to convert this feature on the newer Vue.js stack. Do you have any portion of the application (on Vue.js) that would be similar so I could take some inspiration from it?

Hello @Vitaliy-1, thanks for the comments, if they are still relevant, I will take a look at those once the refactor is done.