As a data curator, I'd like to be able to use the GUI to deaccession multiple datasets
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
While checking deposits in the Harvard Dataverse Repository, I occasionally have to deaccession multiple datasets that don't contain data (they often contain only research articles) while I learn more from the depositor about their intentions and data availability.
Deaccessioning reduces the chance that deposits will appear when people are looking for data and gives the depositors a chance to create new dataset versions with data. (If the depositor can't add data or doesn't reply, I later delete the published deposit.)
When I need to deaccession multiple datasets, I have to do so by visiting each dataset page. It would be a lot faster to be able to deaccession multiple datasets at once using the GUI. It's already possible using the Dataverse API.
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 examining the existing GUI flow for deaccessioning one dataset and the already-supported Dataverse API operation. Define how users select multiple datasets and confirm the action; done means multiple datasets can be deaccessioned through the GUI without visiting each dataset page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100