Feature Request: Manage available standard license terms for Dataverse collections
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
Available standard licenses can be managed with native API https://guides.dataverse.org/en/6.7.1/api/native-api.html#manage-available-standard-license-terms . This configuration is valid for all Dataverse collections, but sometimes it is necessary to restrict the available license for a specific Dataverse collections.
What kind of user is the feature intended for?
Sysadmin
What inspired the request?
A dataverse collection for self-deposit, the curators should only be able to apply one license.
What existing behavior do you want changed?
Configuration of standard licenses for Dataverse collections. Maybe like the API to limit the available licenses for a dataset https://guides.dataverse.org/en/6.7.1/api/native-api.html#set-available-licenses-for-a-dataset-type
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 reading the linked native API documentation for managing standard license terms and the dataset license endpoint. Define how collection-level restrictions should be configured and enforced for curators; done means a Dataverse collection can limit its available standard licenses independently of the global configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100