openlibhums / openlibhums/janeway

Open peer review feedback

Open
#4,148 3 comments 1 reaction 3 assignees View on GitHub

@S-Haime is already working on this.

Since May 1, 2024.

enhancement new feature UX
Dominant language
Python
Stars
238
Forks
97
Avg merge
9d 1h
Merged PRs (30d)
8

Description

Feedback from JR - Glossa. FD 8198
"With respect to Open Peer review, my request is even more specific, as I would like to see this as a reviewer-driven option in Janeway (which would make it unique, really, and allow us to socialize OPR more easily):

  1. the reviewer decides:

a. whether their review is made available online alongside the article (reansparent peer review)

b. whether they wish to sign their review when it is made available (fully open peer review).

So this needs two separate buttons available to the reviewer in the reviewer pane.

  1. Clicking ‘yes’ on (1a) automatically (easy for me to say, right?) turns the reviewer’s .pdf review into a supplementary file with its own dependent DOI. This is signaled to SiliconChips who refer to that review and the dependent DOI at the end of the article under a new section called ‘Peer Reviews’ (as they already do not for hosted additional material Janeway hosts for the authors)

  2. Clicking ‘yes’ on (1b) asks the reviewer to update their ORCID and afilliation, and the reviewer’s name, ORCID and affiliation are accordingly published in front of the dependent DOI leading to the review in the PDF and the XML of the article. Again this should lead to a visible isntruction for SiliconChips to insert that reviewer name in the relevant ‘Open Reviews section of the article.

This will minimize the work of the editor, which has always been my greatest fear with Open Peer review: having to curate 4 papers (the paper and 3 reviews) instead of just the paper."

Johan / @ajrbyers / @S-Haime may wish to have meeting to discuss.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.