openlibhums / openlibhums/janeway
As an editor I want to avoid inviting a co-author as a reviewer by mistake
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 238
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
User story
Anonymized report from editor:
"I accidentally invited a co-author to review a paper. I feel really embarrassed, but I also think this was a mistake that was very easy to make and could be prevented. I am pretty sure it happened because I didn't realize there were co-authors because the review system only shows the first author, and you have to click on the Editor Assignment to see the full author list. Usually I will see this when I'm assigned a paper at the Unassigned stage, but it's really hard to see after it gets in the Review list, and since the paper was transferred."
Proposed solution
"...I wonder if there is anything that can be done in Janeway, either to give a warning if you try to invite an author of the paper, or to be able to see the full author list more easily when making the assignments."
Notes from Dev team
- As an editor when I am making a peer review assignment, if I select an author of the paper as a reviewer, I should see a warning message.
- As an editor, when I'm in the review stage of a paper, I can see all the authors assigned to it (rather than just the correspondance author)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the editor peer-review assignment flow and the review-stage paper view described in the issue. Check how authors and reviewers are currently loaded and displayed. Done means an editor is warned when selecting a paper author and can see the full author list while assigning reviews.
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