-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Submissions schema filters out declined&cancelled review assignments #10076
Comments
Editors, Authors and Reviewers have access to the new dashboard. It might have sense to separate mapping of the submissions for editors from other roles, as it includes more data, for which authors and reviewers shouldn't have access to. Declined and cancelled reviews are such an example. My proposal is to create a separate mapping for editor's list, e.g. |
I'm wondering if rather than a separate mapping, it would be possible to do this via some sort of permissions, e.g. an editor would have the extra review assignments included because they have permission to access them. That way we won't be maintaining multiple mappings that re similar but not exactly the same. I'll do some thinking on what that could look like and if that makes sense with the existing model we have in place. |
I'm currently working on adopting laravel permissions library but that's a long road |
@Hafsa-Naeem, I believe that the best approach here would be to create a separate submission mapping for authors (or editors). It could be together with a new endpoint or using the same endpoint ( |
@Vitaliy-1 I don't know whats better fit how to achieve it with current architecture. But just from API point of view if there is field or information that certain role should not have access to - my suggestion would be - just don't include it. For example in graphql where you could ask for lots of different data - common practice there would be to return null if you don't have permissions to access something. |
In the submission schema we have the method that defines mapping return $this->mapByProperties($this->getSubmissionsListProps(), $item, $anonymizeReviews); On the top of my head, we can do the separate mapping for authors:
In contrast, the schema and endpoint for editors should include info regarding declined and cancelled review assignments |
@Vitaliy-1 Ready for review |
…review assignments
…review assignments
…review assignments
Thanks, added a review |
…ilter roles only from relevant (review) stages
…ilter roles only from relevant (review) stages
@Vitaliy-1 Ready for review again |
Thanks! I left a comment for a change to ensure that we are a given full information to a user about reviews in a stage, to which the person is assigned to. This might be relevant for OMP. |
…er roles only from relevant (review) stages
…g application-defined review stages
…er roles only from relevant (review) stages
…pplication-defined review stages
…t, and fixed docblock.
…review_assignments #10076 show declined/cancelled reviews to editors
…eview_assignments pkp/pkp-lib#10076 Show declined/cancelled reviews to editors & update submodule reference
…eview_assignments pkp/pkp-lib#10076 Added getReviewStages method to Application class
Describe the issue
On new submission listing we would like to indicate for editors also review assignments that has been declined or cancelled. Currently Submissions Schema filters them out - https://github.com/pkp/pkp-lib/blob/main/classes/submission/maps/Schema.php#L422
The new submission listing is using the api/_submissions endpoint .
What application are you using?
OJS, OMP or OPS version 3.5
The text was updated successfully, but these errors were encountered: