<html 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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">We also tend to use refIDs for digitization. We’ve tried to look at their length and semantic meaninglessness as an advantage, and an opportunity to examine our workflows for places where colleagues are doing a lot of manual data entry,
and to replace those points with API calls or some other form of automation that doesn’t force folks to do a lot of copying and pasting. The `find_by_id` endpoint is super useful for this.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Another option are ArchivesSpace’s external IDs. You can save as many as you want and, more importantly, you can specify where the identifier comes from, which can be super useful if you have an environment where there are multiple identifier
sets which get used for specific things. Although these aren’t visible in the UI by default, it looks like you can turn them on in the config.rb file:
<a href="https://archivesspace.github.io/archivesspace/user/configuring-archivesspace/">
https://archivesspace.github.io/archivesspace/user/configuring-archivesspace/</a> I’m not sure if these get exported in EAD or anything, but thought I’d throw that out there as an option.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hillel<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black"><archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of "Pruitt, Adrienne" <Adrienne.Pruitt@tufts.edu><br>
<b>Reply-To: </b>Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Date: </b>Tuesday, November 6, 2018 at 11:22 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>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for all of your very helpful responses, everybody!
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">We have been investigating use of the digitization plug-in, which looks great. However, our digitization workflow (especially digitization on demand) usually involves items that don’t have pre-existing metadata,
which makes it less suitable at the moment, since our display system requires item-level metadata. As we move into a system that can handle complex objects, and also try out the PUI, it sounds like there are a couple of solutions here that might work for us.
We will probably be contacting some of you with further questions – thanks again!</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">-Adrienne</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<b>On Behalf Of </b>Noah Huffman<br>
<b>Sent:</b> 6 November 2018 11:10 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></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">John’s message reminded me that at Duke, our repository items have externally-minted and persistent ARKs. When we created digital object records in ASpace based on our repository objects using the service I described
previously, we store those ARKs in the digital object identifier field in ArchivesSpace. So, basically we have two identifiers that connect records in ArchivesSpace with records in our repository (the refID and the ARK). In our shop, the refID is really useful
for starting and facilitating the digitization workflow, but the ARK is more stable.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">I’m still not sure we have the most elegant setup and there are a lot of identifiers floating around, but it seems to be working for us so far…</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">-Noah</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
<b>On Behalf Of </b>Rees, John (NIH/NLM) [E]<br>
<b>Sent:</b> Tuesday, November 6, 2018 10:59 AM<br>
<b>To:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Component unique identifiers<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Wow, this is super helpful. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">We’ve been noodling on a similar use case. All our existing repository projects leverage our MARC 035 field ids (Voyager ILS-supplied) to mint ids/Fedora PIDs, but now we’re embarking on ASpace projects that don’t always have a Voyager
record, or have ID minting practices from other external systems that we can’t replicate in ASpace - or maybe don’t want to.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">We’re still struggling with what the ID should actually be – we’re wary of using internally-generated IDs.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">John<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">John P. Rees<o:p></o:p></p>
<p class="MsoNormal">Archivist and Digital Resources Manager<o:p></o:p></p>
<p class="MsoNormal">History of Medicine Division<o:p></o:p></p>
<p class="MsoNormal">National Library of Medicine<o:p></o:p></p>
<p class="MsoNormal">301-827-4510<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>From:</b> Rachel Aileen Searcy <<a href="mailto:rachel.searcy@nyu.edu">rachel.searcy@nyu.edu</a>>
<br>
<b>Sent:</b> Tuesday, November 06, 2018 9:38 AM<br>
<b>To:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Component unique identifiers<o:p></o:p></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=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=egSNa_E82CniRdk2kD1V-niZbqO7XVArIMZPAwDN1cs&s=T7i8Vt9h589_N4UGea1yf4aXt6K5RSTeDqaAG4Tcg3U&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=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=egSNa_E82CniRdk2kD1V-niZbqO7XVArIMZPAwDN1cs&s=sxduklMTsEb7_XFdBr5_vnRGHkUGLA6omAWn1IGBo1s&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&d=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=egSNa_E82CniRdk2kD1V-niZbqO7XVArIMZPAwDN1cs&s=fOyyOc5DCDx0rAcVskO3M1WWo02JAOrFVrU1bGprZQ4&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-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<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-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">Hello, all,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="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><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Segoe UI";color:black"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">Thank you!</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="color:black">Adrienne Pruitt </span></b><span style="font-size:9.0pt;color:black">| Collections Management Archivist</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;color:black">Digital Collections and Archives</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;color:black">Tufts University</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="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;color:black"> |<span style="background:white">617-627-0957</span></span><o:p></o:p></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>