Edit a role in a collection using Native API
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
Roles can be created in a collection using the API or the UI, but can only be edited using the UI.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
API User
Needed for the SPA frontend to edit roles
What inspired the request?
Edition bug of such roles in the UI:
Any brand new behavior do you want to add to Dataverse?
Add a PUT request method to /api/dataverses/$ID/roles similarly to the one to edit global roles:
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 by reviewing the existing collection-role API at /api/dataverses/$ID/roles and the global-role editing approach in pull request #10612. Compare the related issues, then define done as a PUT request that lets API users edit roles in a collection for the SPA frontend.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, authorization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100