Feature Request: Add the ability to apply an embargo to just the abstract and not all of the metadata
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
What kind of user is the feature intended for?
Guest
What inspired the request?
Current requirement from submitter.
What existing behavior do you want changed?
Modify embargos to metadata
Any brand new behavior do you want to add to Dataverse?
Add the ability to apply an embargo to just the abstract and not all of the metadata.
Any open or closed issues related to this feature request?
Not from what I've seen.
Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?
No but it has come up as a necessity.
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
No files, tests, or entry points are named. Start by tracing how Dataverse currently applies metadata embargos, then clarify the intended distinction between abstract and other metadata with the requester. Done means the selected abstract can be embargoed while the remaining metadata stays available, with behavior verified by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100