Feature Request/Idea: Update user guide to better reflect how embargos are set up.
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
It should be clear how to set up embargoes for Datasets and Files.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
What inspired the request?
I tried to understand how to enact embargoes via the User Guide, and was unsuccessful.
What existing behavior do you want changed?
The User Guide should be more clear as to the procedure to getting it done.
Any brand new behavior do you want to add to Dataverse?
Any related open or closed issues 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
The issue points to the User Guide and asks for clearer instructions for setting up embargos on Datasets and Files. Start by locating the relevant User Guide sections and reviewing the existing procedure. Done means a user can follow the guide to enact both types of embargoes without needing additional instructions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100