<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Just a +1 for the NYU Digitization Work Order plugin. We make use of that plugin at Duke in our digitization workflow, although instead of adding component unique
identifiers we just use the Ref ID field as the key that unites our digital object metadata (stored in Fedora) with ASpace. For the most part, we have abandoned semantic filenames so that we can accommodate existing filenames for born-digital materials and
filenames that may have been generated by other units on campus that we might not control.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We created a service in our repository that can post (in batch) very basic digital object records to ArchivesSpace and then link those digital objects to existing
archival objects using the ASpace ref_ID values stored in our repository. Then, we can publish finding aids that include links to digital objects in our repository and well as embedded image, audio, and video files.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Happy to explain more if folks are interested,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-Noah<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#404040"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#404040">================<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#404040">Noah Huffman<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#404040">Archivist for Metadata, Systems, and Digital Records<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#404040">David M. Rubenstein Rare Book & Manuscript Library<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#404040">Duke University | 919-660-5982<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#404040"><a href="http://library.duke.edu/rubenstein/"><span style="color:#404040">http://library.duke.edu/rubenstein/</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org>
<b>On Behalf Of </b>Rachel Aileen Searcy<br>
<b>Sent:</b> Tuesday, November 6, 2018 9:38 AM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Component unique identifiers<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi Adrienne,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We had a similar issue here at NYU. Previous digitization projects relied on the shorter Archivist's Toolkit refids for file naming, but this became untenable with those created by ArchivesSpace. We didn't want to change our inter-departmental
workflows too radically, so we contracted with HM to develop a plugin called the Digitization Work Order plugin (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_hudmol_digitization-5Fwork-5Forder&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=a8VhzFOWwpTiqB1van_vrBlDJZ3W0W2hIqSQFWtyA7o&s=oGY6499D7rcudpNsvJYpkct1MJgdGPGj-M44Pg9DlNI&e=">here
on github</a>). This plugin allows the user to select individual components from a resource record (including all if desired), which are then assigned sequential component unique identifiers that can be used for file naming or other purposes. The plugin also
produces a csv of descriptive information of those components, and automatically inserts this newly created identifier into the components Component Unique Identifier field. We have some demo slides
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__guides.nyu.edu_ld.php-3Fcontent-5Fid-3D26740399&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=a8VhzFOWwpTiqB1van_vrBlDJZ3W0W2hIqSQFWtyA7o&s=DU2fH99VS6HGDcQwtaqNbP70YUuUHHzoiAvKfOybgk0&e=">
here</a>, as well as <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_11kWxbFTazB6q5fDNBWDHJxMf3wdVsp8cd7HzjEhE-2Dao_edit-23&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=a8VhzFOWwpTiqB1van_vrBlDJZ3W0W2hIqSQFWtyA7o&s=-JgXLLuZk9sdTeKhnhLQgx03FobqKtmMxNdXVopJOcI&e=">
instructions</a> in our local ArchivesSpace manual. I'd also be happy to talk further to answer any questions.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Rachel<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, Nov 5, 2018 at 2:54 PM Chris Mayo <<a href="mailto:mayoc@bc.edu">mayoc@bc.edu</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">Hi Adrienne,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We ran into a similar issue at Boston College when we migrated from to ASpace from Toolkit. Our practice had been to combine the collection ID with an auto-generated refID to create component unique identifiers, but the auto-generated refIDs
in Aspace were much too long for our needs. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">What we eventually wound up doing is using the database primary key for a given archival object as the unique part of its component unique ID, so that any given for an archival object we're planning to digitize gets a CUI with the format
of 'mmsID_NNNNN" where the numerical portion is pulled from the 'archival_object_NNNNN' at the end of the archival object's URL. The really handy part of this is that it lets us parse our CUIs to make API calls. It's also robust to rearrangement, if you are
only moving the archival object around within the collection hierarchy - the database key remains the same. It doesn't survive reprocessing, however, if you are deleting/rebuilding/combining archival objects, so we always make sure to begin the process of
digitization after a collection has been processed or reprocessed. It makes the CUIs somewhat semantically meaningful - but only if you know what you are looking at. We're still not sure how we feel about that, but it's what works for us for now.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Hope that helps!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Best,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Chris<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, Nov 5, 2018 at 11:00 AM Pruitt, Adrienne <<a href="mailto:Adrienne.Pruitt@tufts.edu" target="_blank">Adrienne.Pruitt@tufts.edu</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Hello, all,</span><span style="font-size:13.5pt;font-family:"Segoe UI",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="font-size:13.5pt;font-family:"Segoe UI",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">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 identifier<span style="background:white">s 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.</span> We’re interested to hear how others are handling their identifiers (particularly in regards to digitization workflows.)</span><span style="font-size:13.5pt;font-family:"Segoe UI",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Segoe UI",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Thank you!</span><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Adrienne Pruitt </span></b><span style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:black">| Collections Management Archivist</span><span style="font-size:13.5pt;font-family:"Segoe UI",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:black">Digital Collections and Archives</span><span style="font-size:13.5pt;font-family:"Segoe UI",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:black">Tufts University</span><span style="font-size:13.5pt;font-family:"Segoe UI",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:adrienne.pruitt@tufts.edu" target="_blank"><span style="font-size:9.0pt">adrienne.pruitt@tufts.edu</span></a></span><span style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:black"> |<span style="background:white">617-627-0957</span></span><span style="font-size:13.5pt;font-family:"Segoe UI",sans-serif;color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=S8ME4Fo5XAeEtz-SEJljWkmvBYIPb_6ILuGWdUkOXtE&s=fTvu_1amNaLXp4WRGkvgY0OdpV3LaA82ly7l70dQZjc&e=" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<br>
-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#888888">Chris Mayo</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#888888">Digital Production Librarian</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#888888">Thomas P. O'Neill, Jr. Library</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#888888">Boston College</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span style="color:#888888"><a href="mailto:chris.mayo@bc.edu" target="_blank">chris.mayo@bc.edu</a></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=S8ME4Fo5XAeEtz-SEJljWkmvBYIPb_6ILuGWdUkOXtE&s=fTvu_1amNaLXp4WRGkvgY0OdpV3LaA82ly7l70dQZjc&e=" target="_blank">https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=S8ME4Fo5XAeEtz-SEJljWkmvBYIPb_6ILuGWdUkOXtE&s=fTvu_1amNaLXp4WRGkvgY0OdpV3LaA82ly7l70dQZjc&e=</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Rachel Searcy<br>
Accessioning Archivist, Archival Collections Management<o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt">New York University Libraries</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">212.998.2539 | <a href="mailto:rachel.searcy@nyu.edu" target="_blank">
rachel.searcy@nyu.edu</a> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>