[Archivesspace_Users_Group] Component unique identifiers

[Pruitt, Adrienne]

Hello, all,

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.)

Thank you!

Adrienne Pruitt | Collections Management Archivist
Digital Collections and Archives
Tufts University
adrienne.pruitt at tufts.edu<mailto:adrienne.pruitt at tufts.edu> |617-627-0957
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20181105/0698ef3c/attachment.html>