dataset name uniqueness issue: do not allow same dataset name in Dataverse
Open
Nobody has claimed this yet.
Feature: Publishing & Versions
Type: Feature
User Role: Curator
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Users are able to create datasets with identical names. This is problematic and allows coauthors to have two separate DOIs for the same dataset, also allows versioning updates to happen in one and potentially not the other, etc ....
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 tracing the dataset creation path and the existing uniqueness rules in Dataverse. Clarify whether names must be unique globally or within another scope, then define how duplicate creation should be rejected without disrupting DOI or versioning behavior. Done means identical dataset names can no longer create conflicting datasets, with tests covering the chosen scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100