Skip to content
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

Section editors can access submission and data only if they are assigned to that submission #2109

Closed
bozana opened this issue Dec 16, 2016 · 5 comments

Comments

@bozana
Copy link
Collaborator

bozana commented Dec 16, 2016

At the moment section editors can access submission either if they are assigned to the section, that submission is assigned to, or if they are assigned to the submission.
In case of some file downloads, currently the section editors are only permitted to download a file if the file submission is assigned to their section, which is wrong -- a section editor does not have to be assigned to a section. S. also http://forum.pkp.sfu.ca/t/ojs-3-the-current-role-does-not-have-access-to-this-operation/24614
Thus, it would be best not to consider the section assignment at all, but only if the section editor is assigned to that submission.

Note: if a section has section editors assigned, all submissions having that section will first automatically be assigned to those section editors.

@bozana
Copy link
Collaborator Author

bozana commented Dec 16, 2016

PRs:
pkp-lib ojs-stable-3_0_1: #2110
ojs ojs-stable-3_0_1: pkp/ojs#1148 (just submodule update for the tests)
pkp-lib master: #2116
ojs master: pkp/ojs#1154 (just submodule update for the tests)
omp master: pkp/omp#369 (just submodule update for the tests)

@bozana
Copy link
Collaborator Author

bozana commented Dec 19, 2016

@asmecher, could you code review the PR above? I tested it with OMP as well -- it should be OK. This is for ojs-stable3_0_1, but if OK, I will cherry-pick it to master too...

@asmecher
Copy link
Member

Thanks, @bozana -- this is a pretty profound change, but luckily not too big, and I do think it'll relieve a lot of confusion around submission access. Please go ahead.

@asmecher
Copy link
Member

@stranack, FYI: this change means that Section Editors no longer automatically get access to submissions based on the section that it's assigned to. It only matters what submissions a section editor is assigned to. However, Section Editors get automatic assignments to new submissions in their sections.

This makes it explicit which submissions a section editor has access to, and e.g. removing a section editor's assignment to a submission will really mean they don't have access any more, even if that submission is in a section they're configured as section editor for.

Clear as mud? :)

bozana added a commit that referenced this issue Dec 20, 2016
#2109 sub editors access policy
bozana added a commit to pkp/ojs that referenced this issue Dec 20, 2016
pkp/pkp-lib#2109 submodule update ##bozana/2109##
bozana added a commit to bozana/pkp-lib that referenced this issue Dec 20, 2016
bozana added a commit that referenced this issue Dec 20, 2016
bozana added a commit to bozana/ojs that referenced this issue Dec 20, 2016
bozana added a commit to bozana/omp that referenced this issue Dec 20, 2016
bozana added a commit to pkp/ojs that referenced this issue Dec 20, 2016
bozana added a commit to pkp/omp that referenced this issue Dec 20, 2016
@bozana
Copy link
Collaborator Author

bozana commented Dec 20, 2016

everything merged, thus closing...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants