Support Archival Resource Key (ARK) as Persistent Identifier
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Currently, dataverse supports DOIs and Handles as persistent identifiers, but ARK is a viable alternative, that can be very enticing, especially due to the price (it's free).
Details about ARK: https://n2t.net/e/ark_ids.html
To provide ARKs, one must either have an access to an ARK provider like EZID (https://ezid.cdlib.org/) or register your organization as a Name Assigning Authority (NAA) and be an ARK provider, possibly using the dataverse.
As different dataverses inside a Dataverse installation may belong to different organizations, it may be a requirement for each (at least top-level) dataverse to have a NAA assigned.
I will try to look at the Handle and DOI implementation and try to come up with a way to implement ARK support with minimal intrusion.
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 existing Handle and DOI implementations and reading the linked ARK specification. Determine how provider access and per-dataverse Name Assigning Authority configuration should fit those integrations; done means Dataverse can create and manage ARK persistent identifiers alongside DOI and Handle support.
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
- 25/100