Story #6440

Keep DOI registrations current and resolvable

Added by ben leinfelder about 6 years ago. Updated over 4 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


We have used a few different DOI registration approaches on the KNB:
  • bulk load of all historical content (metadata and data) when we became a DataONE MN - uses the "d1/object/<pid>" endpoint for resolution
  • publish requests during our UI testing stage - uses "/m/#view/<pid>"
  • new publish requests now that we are deploying Metacat UI at the web root.

Generalizing this to other Metacat deployments with EZID accounts, it is reasonable to assume that their registrations drift as they migrate serves or change endpoints and it would be great to address our needs on the KNB as well as any other MNs that also manage DOIs via EZID.

Related issues

Related to Metacat - Support #6793: Update DOIs from KNB to redirect to view serviceIn Progress07/02/2015


#1 Updated by ben leinfelder about 6 years ago

  • Description updated (diff)

#2 Updated by ben leinfelder almost 6 years ago

  • Assignee set to Lauren Walker
  • Status changed from New to In Progress

There is now a section in the metacat admin screen (replication configuration) for updating DOIs. Three input choices: specific DOIs, specific formatIds or all EML documents.

#3 Updated by ben leinfelder almost 6 years ago

Modified the EZID java library and the Metacat DOIService to use the multithreaded ezid client class. This should help speed-up batch updates. Note that we should tag a release of EZID lib when we are happy with this approach. Currently using 1.0.1-SNAPSHOT

#4 Updated by ben leinfelder over 4 years ago

  • Status changed from In Progress to Closed

We now have a few mechanisms in place to keep DOI registrations updated and can always trigger them manually for individual objects or types of objects.

Also available in: Atom PDF