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

Feature Request/Idea: Select more default roles for dataset creators in the UI than Contributor and Curator #10005

Open
DS-INRAE opened this issue Oct 12, 2023 · 1 comment
Labels
Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. Feature: Permissions Type: Suggestion an idea User Role: Superuser Has access to the superuser dashboard and cares about how the system is configured UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF

Comments

@DS-INRAE
Copy link
Member

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?

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?

@pdurbin pdurbin added Type: Suggestion an idea Feature: Permissions User Role: Superuser Has access to the superuser dashboard and cares about how the system is configured Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF labels Oct 13, 2023
@DS-INRAE
Copy link
Member Author

Putting this issue in "Interest" rather than "Needed" for us to prioritize the SPA issue :

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. Feature: Permissions Type: Suggestion an idea User Role: Superuser Has access to the superuser dashboard and cares about how the system is configured UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF
Projects
Status: 🔍 Interest
Development

No branches or pull requests

2 participants