search

pulibrary / aspace_helpers

methods and reports to support common SC activities in ArchivesSpace
1 stars 0 forks source link

does EZID have to be updated when a call number changes? #361

Closed regineheberlein closed 1 year ago

regineheberlein commented 1 year ago

This is a question from Will C. They need to change the call numbers for a handful of collections. He is wondering whether they need to update the URLs for those ARKs in EZID.

regineheberlein commented 1 year ago

Mock example:

MC100, which has ark123, is now going to be called MC101, and the question is: do we need to update EZID to bind MC101 to ark123; or do we need to do nothing; or do we need to mint a new ark.

regineheberlein commented 1 year ago

Having consulted with colleagues, the best way forward for a call number that needs to change is to update the ARK binding to point to the new URL.

regineheberlein commented 1 year ago

@Will-Clements NB If it's more than a few collections, we can also automate this.

regineheberlein commented 1 year ago

Not what you asked, but since the use case here is a location change: can you get away with just AbID'ing the containers and leaving the call number in place? That way you don't have to worry about fallout like stale citations, usage statistics etc.

FWIW there's always been a handful of collections that break the call number prefix-to-repository association anyway, including the TC's and WC's.