openlibhums / openlibhums/janeway

As an editor working in a team, I want to be anonymous until peer review is complete

Open
#3,333 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

User story
As a senior editor with an established reputation in my field, if I give constructive criticism on a manuscript submitted to my journal, the author usually respects it and is willing to revise accordingly. However, I often assign submissions to junior editors to manage peer review, and I have seen this introduce unneeded drama and doubt, because authors can find issue with the individual editor in order to disagree with the assessment of their work, even if the assessment is sound.

Describe the solution you'd like
We'd like the editor's name to be concealed until peer review is complete. This would entail hiding some metadata in the author's article status view as well as making sure the editor's name wasn't in emails sent during revision requests.

Describe alternatives you've considered
Communicating through the senior editor's account, but this is cumbersome and keeps us from managing editor assignments through Janeway.

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.

Research direction

Start by tracing the author's article status view and the emails sent during revision requests, since the issue identifies both as places where the editor's name must be concealed. Done means the editor remains anonymous in those contexts until peer review is complete while editor assignments continue to work through Janeway.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.