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

Abstracts: Introduce tighter controls on modification #3431

Closed
pferreir opened this issue Jun 26, 2018 · 2 comments · Fixed by #4530
Closed

Abstracts: Introduce tighter controls on modification #3431

pferreir opened this issue Jun 26, 2018 · 2 comments · Fixed by #4530
Assignees
Projects
Milestone

Comments

@pferreir
Copy link
Member

pferreir commented Jun 26, 2018

Right now, all authors/speakers can modify an abstract. While this is a sensible default for most events, in larger ones, stricter controls may be required. A good example is the JACoW workflow, according to which:

  • Speakers should have submission rights (uploading files);
  • Only primary authors should be able to edit the title/description and authors of the abstract;

This should be ideally configurable.

@pferreir pferreir added this to the v2.3 milestone Jun 26, 2018
@ThiefMaster ThiefMaster added this to To do in Release 2.3 via automation Jul 6, 2020
@ThiefMaster
Copy link
Member

Speakers should have submission rights (uploading files);

Is this about who gets submission privileges after the abstract has been accepted? Because if yes, I'd say this should be a separate issue since it has nothing to do with editing abstracts.

Only primary authors should be able to edit the title/description and authors of the abstract;

So simply not giving co-authors any special access on the abstract except being able to see it?

@pferreir
Copy link
Member Author

pferreir commented Jul 9, 2020

Yeah, that's it, @ThiefMaster

@Leats Leats self-assigned this Jul 9, 2020
@Leats Leats moved this from To do to In progress in Release 2.3 Jul 10, 2020
@Leats Leats moved this from In progress to Review in progress in Release 2.3 Jul 13, 2020
Release 2.3 automation moved this from Review in progress to Done Jul 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Release 2.3
  
Done
Development

Successfully merging a pull request may close this issue.

3 participants