Feature Request/Idea: Select more default roles for dataset creators in the UI than Contributor and Curator
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
Currently only Contributor and Curator roles may be selected as default roles from the UI. It can be done via API (https://guides.dataverse.org/en/latest/api/native-api.html#assign-default-role-to-user-creating-a-dataset-in-a-dataverse-collection) but even in this case any modification via the UI makes the API set role impossible to be set via UI again.
In order not to clogg the selection and provide too many choices that may confuse users, it might be best to make the list of possible default roles configurable rather than having all roles always usable as default.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Dataverse collection Admins setting up roles for Depositors
What inspired the request?
- https://github.com/IQSS/dataverse/issues/9938 : this is a split off of one of the item mentioned in this issue.
What existing behavior do you want changed?
Expand the choices in the Permissions menu to be able to use other roles than Contributor and Curator
Any brand new behavior do you want to add to Dataverse?.
Maybe this should be done only in the new UI as even if not convenient, the desired result can be achieved via API
Any open or closed issues related to this feature request?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Permissions menu's default-role selection and the native API endpoint linked in the issue. Done means collection administrators can select additional default roles in the UI, with the configurable-choice scope clarified for the current or new UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authorization, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100