Feature Request: Change embargo settings via GUI
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
Since DV v5.8 there is the very useful option of setting embargoes. But after the embargo was set and the data set was published, the embargo can only be changed from the superuser using the API.
What kind of user is the feature intended for?
Curator, Superuser
What inspired the request?
We cannot use the embargo function because the depositors want to change the embargo very often and the curators are not familiar with the API functionality.
What existing behavior do you want changed?
The modification of embargo settings for published datasets with the GUI, not only via API:
/api/datasets/$dataset-id/files/actions/:set-embargo
/api/datasets/$dataset-id/files/actions/:unset-embargo
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 GUI for published dataset file settings and the two referenced actions: /api/datasets/$dataset-id/files/actions/:set-embargo and /api/datasets/$dataset-id/files/actions/:unset-embargo. Trace how these API actions are exposed and identify the relevant GUI entry point. Done means curators and superusers can change published-dataset embargo settings through the GUI, with behavior matching the API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100