document request reviewers #847
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zzacharo
force-pushed
the
document-request-reviewers
branch
2 times, most recently
from
4b0c76d to
c7df75b
Compare
zzacharo
force-pushed
the
document-request-reviewers
branch
from
c7df75b to
bdd624a
Compare
ntarocco
reviewed
Aug 25, 2025
| - may require clarifications (i.e. a conversation) between the creator of the request and the recipient(s) | ||
| - may expire after a certain amount of time | ||
|
|
||
| ### Reviewers in Requests | ||
|
|
||
| Reviewers are optional participants in the request process who can be assigned to provide expert opinion, feedback, or recommendations. Unlike the receiver who makes the final decision to accept or decline the request, reviewers serve as consultants or advisors. |
There was a problem hiding this comment.
I would use the terms consultant or advisor:
Suggested change
| Reviewers are optional participants in the request process who can be assigned to provide expert opinion, feedback, or recommendations. Unlike the receiver who makes the final decision to accept or decline the request, reviewers serve as consultants or advisors. | |
| Reviewers are optional participants in a request process. They provide expert opinions, feedback, or recommendations but cannot make the final decision to accept or decline the request. That responsibility lies solely with the receiver. |
docs/operate/customize/requests.md
Outdated
| @@ -0,0 +1,72 @@ | |||
| # Requests | |||
|
|
|||
| _Introduced in InvenioRDM v14_ | |||
There was a problem hiding this comment.
Suggested change
| _Introduced in InvenioRDM v14_ | |
| _Introduced in v14_ |
docs/operate/customize/requests.md
Outdated
|
|
||
| Configure the requests system in InvenioRDM, including the reviewers feature for enhanced review workflows. | ||
|
|
||
| ## Reviewers Configuration |
There was a problem hiding this comment.
I don't think we should use CamelCase for titles (as always suggested by LLMs). Applicable to all new titles.
Suggested change
| ## Reviewers Configuration | |
| ## Reviewers configuration |
docs/operate/customize/requests.md
Outdated
|
|
||
| ## Reviewers Configuration | ||
|
|
||
| The reviewers feature enables assignment of external experts, collaborators, or community members to provide feedback on requests without granting them decision-making authority. |
There was a problem hiding this comment.
Suggested change
| The reviewers feature enables assignment of external experts, collaborators, or community members to provide feedback on requests without granting them decision-making authority. | |
| The reviewers feature enables assignment of external experts, collaborators, or community members to provide feedback on requests without granting them the possibility of accepting or declining a request. |
|
|
||
| ```python | ||
| # Enable assignment of groups as reviewers (requires invenio-users-resources) | ||
| USERS_RESOURCES_GROUPS_ENABLED = True |
There was a problem hiding this comment.
I would remove this flag (from the code): if groups is enabled, why having this extra flag? Any benefit?
There was a problem hiding this comment.
this is the flag that enable groups in the system, it was not newly added.
There was a problem hiding this comment.
Ah right, then in the doc it is not super clear, in particular the comment
docs/operate/customize/requests.md
Outdated
| USERS_RESOURCES_GROUPS_ENABLED = True | ||
| ``` | ||
|
|
||
| - **Requirements**: Requires the `invenio-users-resources` module to be installed and configured |
There was a problem hiding this comment.
That's always the case in InvenioRDM
Suggested change
| - **Requirements**: Requires the `invenio-users-resources` module to be installed and configured |
docs/operate/customize/requests.md
Outdated
|
|
||
| ## Permissions | ||
|
|
||
| Reviewer assignment requires appropriate community permissions: |
There was a problem hiding this comment.
Suggested change
| Reviewer assignment requires appropriate community permissions: | |
| By default, reviewer can be added or removed by community members with roles: |
Can the submitter assign reviewers?
There was a problem hiding this comment.
We decided not to allow them in the first implementation.
docs/operate/customize/requests.md
Outdated
|
|
||
| Reviewer assignment requires appropriate community permissions: | ||
| - **Owners** and **managers** can assign/remove reviewers | ||
| - **Curators** can assign/remove reviewers (if configured) |
docs/use/communities.md
Outdated
| @@ -126,4 +126,6 @@ In the **Requests** tab, you can view all requests for your community. It allows | |||
|
|
|||
| The request page provides a dedicated space for communication. You can **have a conversation with the submitter** directly within the request, and you can **accept or decline the inclusion request** based on your community's curation policies. | |||
|
|
|||
| You can find the high-level architecture documentation for communities [here](../maintenance/architecture/communities.md). | |||
| When a submission requires expert input or peer review, you can **assign reviewers** to give specific users or groups access to evaluate the request. This allows you to share the request with external experts, collaborators outside your community, or community members who normally wouldn't have access (such as readers). Reviewers can provide feedback on the research publication draft or assess whether a record meets your community's inclusion criteria. They participate in the request conversation and share their expertise to help you make an informed curation decision, while you retain the final authority to accept or decline the request. | |||
There was a problem hiding this comment.
Suggested change
| When a submission requires expert input or peer review, you can **assign reviewers** to give specific users or groups access to evaluate the request. This allows you to share the request with external experts, collaborators outside your community, or community members who normally wouldn't have access (such as readers). Reviewers can provide feedback on the research publication draft or assess whether a record meets your community's inclusion criteria. They participate in the request conversation and share their expertise to help you make an informed curation decision, while you retain the final authority to accept or decline the request. | |
| When a submission requires expert input or peer review, you can **assign reviewers** to give specific users or groups access to review the inclusion request. This allows you to share the request with external experts, collaborators outside your community, or community members who normally wouldn't have access (such as readers). Reviewers can provide feedback on the research publication draft or assess whether a record meets your community's inclusion criteria. They participate in the request conversation and share their expertise to help you make an informed curation decision, while you retain the final authority to accept or decline the request. |
while you retain the final authority to accept or decline the request.
Unclear, who is you?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #847