Support IGSN IDs
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
As presented at the last Dataverse, DataCite now supports IGSN identifiers, identifier for material samples.
Dataverse should be able to use these identifiers, leveraging the existing workflow for DOIs.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Depositor identifying samples
What inspired the request?
Need for repositories to use IGSNs rather than DOIs.
Any brand new behavior do you want to add to Dataverse?
Ability to register a PID providing service for IGSNs.
Any open or closed issues related to this feature request?
- https://github.com/IQSS/dataverse/issues/5082
Maybe it already possible given this last issue, and the effort needed would be simply to document that Dataverse now supports these identidfiers.
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 DOI workflow and related issue #5082, then compare those requirements with DataCite's IGSN support. Determine whether documenting existing support is sufficient or whether PID registration changes are needed. Done means IGSN identifiers can be registered through the appropriate workflow, or their existing support is clearly documented.
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
- Mostly clear
- Newbie friendliness
- 30/100