Repository navigation
[Minor update] | Text additions in reviewer invite workflow #281
Description
Valid Title
- I have updated the title to accurately reflect the bug description. Example of a title: [Peer Review] | Reader View - Article landing page, Missing dynamic values
Description
Hi, can you please add subtitle lines to the following reviewer report submission form?
Step 3: Download and Review
Under "For author and editor", please add: "These comments will be made available on the public website alongside the article. Please also include any actual or perceived conflicts of interest transparently in this section as per the reviewer guidelines."
Under "For Editor" please add "These comments are private between you and the editor."
Steps to Reproduce
- Login as a reviewer that has an open assignment.
Expected Result
Include a little more information.
Actual Result
--
Environment Details
No response
Additional Information
I think it is referring to here (Did some mocks):
Metadata
Metadata
Assignees
Labels
No labels
Activity
Tribunal33 commentedon Jun 26, 2026
Minor enhancement to existing functionality. @mreiko please add priority
mreiko commentedon Jun 29, 2026
There are a few ORE content-specific customizations that are listed under the Content epic #140. I have added this ticket to the list.
jardakotesovec commentedon Jul 7, 2026
@1StuJB Hi, just go to this ticket. Reviewer submission screen is still on the legacy stack (most of it). We are considering to modernise it sometime before 3.6 release, but thats not something we could rely on at this point. So we have more technical limitations for these kind of customisations.
But I think what you are suggesting could be universally useful, which would make possible to include it directly to OJS - which is always best for everyone as every customisation has some maintenance/qa cost/burden, as it might require adjustments when updating to newer OJS versions.
Before consulting this with Devika from UX, are you sure you would want to include the Please also include any actual or perceived conflicts of interest transparently in this section as per the reviewer guidelines.". Since there is separate field for competing interests?
1StuJB commentedon Jul 9, 2026
Hi @jardakotesovec, thanks a lot for the update.
For the change under "For author and editor", (only "These comments will be made available on the public website alongside the article."), these are only applicable to open peer review but I think are relevant for reviewers to know as open review is not common among journals. However, I am not sure if these should be hard-coded into OJS for everyone, as not everyone will presumably use open review. I guess this is linked to #255, where for ORE and we have open peer review, that this sentence should be displayed to let the reviewer know that their comments will be made public. For closed review you wouldn't want that text there.
For the competing interest sentence - well caught thank you. Don't include that sentence - that came out of a different thought process when the competing interest box hadn't been turned on. Now the competing interests are available, we don't need that there.
For the change under "For Editor" ("These comments are private between you and the editor."), these will be global for all OJS users presumably. I wanted it added at the same time as the comment above though so that the reviewer has a clear message about which comments will be made public with ORE and which will not be to avoid confusion between the two fields.
Devika008 commentedon Jul 22, 2026
Text description to be included - "These comments will be shared with the author and editor. If this is an open peer review, they will also appear publicly alongside the article."
jardakotesovec commentedon Jul 22, 2026
This change will be included in the next VM update (pkp/pkp-lib#13077).
These texts are included for all OJS users, not just for ORE. Thanks for the suggesting this.
Tribunal33 commentedon Jul 22, 2026
@jardakotesovec I couldn't get this to appear on ORE for basic form. I tried on our local VMs as well. I cleared cache, started new submission, tried new reviewer and old reviewer, tried creating my own form but it didn't display the new text additions.
This is all I could see.
pkp/dev-team#281 Add descriptions for reviewer comments fields
jardakotesovec commentedon Jul 23, 2026
@Tribunal33 Sorry, I did test it locally and than forgot to merge it. It will be there tomorrow when I do another update.
Tribunal33 commentedon Jul 23, 2026
Looks good now. Passed on ORE.
mreiko commentedon Jul 23, 2026
Hi @1StuJB ready for review on the ORE VM.
1StuJB commentedon Jul 27, 2026
Perfect, thank you @mreiko and team. Confirmed approval