openlibhums / openlibhums/janeway

Allow editors to set default review visibility

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

Nobody has claimed this yet.

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

Description

Is your feature request related to a problem? Please describe.
Currently reviews are not visible to authors, by default. They can be made visible on a case-by-case basis, and various parts (text box, custom review form answers, review files) can be made visible individually.

Describe the solution you'd like
An editor who has a business rule of sharing all reviews and review files with authors requested the ability to set default review visibility for completed reviews (except withdrawn reviews). In their words:

"I still think the current display signalling which reviews are visible to the author is a bit confusing. It would be good to have a single button making all available reviews (forms and .pdfs) visible to the author as a default, with the editor able to make some reviews invisible, rather than the other way around as it is now, with the editor having to check every single review for visibility. After all, reviews are for sharing with the author, by default. Many editors, myself included, forget to make one or more reviews available, leading to queries by the author. A single button making existing reviews (not those declined or withdrawn) available would be a great help."

Additional context
I personally am not sure where other editors stand on this. I'm putting in this issue as a proposal that we may or may not adopt.

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

No implementation files, tests, or entry points are identified. First clarify whether the proposal should be adopted and define the visibility rules for completed, declined, and withdrawn reviews; done should include an agreed editor workflow and corresponding coverage for review forms and files.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.