[Archivesspace_Users_Group] Component unique identifiers
ltang5 at lib.msu.edu
Mon Nov 5 14:48:21 EST 2018
Thanks for bringing this up, Adrienne!
Would you (and others) be willing to share your perspective on the following tickets?
I think it would be helpful to hear about the diverse approaches to how CUIs are being used. Ideally, it may also be helpful to upload a sample EAD file to the sandbox (http://test.archivesspace.org/staff/) for developers to “play” with - it would be great to have at least one representative from an institution that has the specific series and box numbering issue, as well as yours.
-on behalf of Dev. Pri.
From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Pruitt, Adrienne" <Adrienne.Pruitt at tufts.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Monday, November 5, 2018 at 11:01 AM
To: "archivesspace_users_group at lyralists.lyrasis.org" <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Component unique identifiers
We’re hoping to move away from semantically meaningful component unique identifiers, but need some way to be able to easily auto-generate a unique identifier that could be used for file-naming purposes in digitization projects. Working with legacy data, we have seen that there can be value in being able to easily associate a binary file floating around on a server somewhere with a relatively easily parsed identifier that links it to its related metadata. However, semantically meaningful identifiers based on collection structure are a rather brittle system prone to breaking when collections are rearranged or reprocessed and easy to mis-enter when working with so many digits. We’re interested to hear how others are handling their identifiers (particularly in regards to digitization workflows.)
Adrienne Pruitt | Collections Management Archivist
Digital Collections and Archives
adrienne.pruitt at tufts.edu<mailto:adrienne.pruitt at tufts.edu> |617-627-0957
More information about the Archivesspace_Users_Group