<div dir="ltr">Hi Adrienne,<div><br></div><div>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://github.com/hudmol/digitization_work_order">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://guides.nyu.edu/ld.php?content_id=26740399">here</a>, as well as <a href="https://docs.google.com/document/d/11kWxbFTazB6q5fDNBWDHJxMf3wdVsp8cd7HzjEhE-ao/edit#">instructions</a> in our local ArchivesSpace manual. I'd also be happy to talk further to answer any questions.</div><div><br></div><div>Best,</div><div>Rachel</div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Nov 5, 2018 at 2:54 PM Chris Mayo <<a href="mailto:mayoc@bc.edu">mayoc@bc.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi Adrienne,</div><div><br></div><div>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. <br></div><div><br></div><div>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.</div><div><br></div><div>Hope that helps!</div><div>Best,</div><div>Chris<br></div></div><br><div class="gmail_quote"><div dir="ltr">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:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div style="direction:ltr;font-family:Tahoma;color:#000000;font-size:10pt">
<div style="font-family:"Segoe UI",Helvetica,Arial,sans-serif;font-size:medium;margin:0px">
<font face="Calibri,sans-serif" size="2"><span style="font-size:11pt">Hello, all,</span></font></div>
<div style="font-family:"Segoe UI",Helvetica,Arial,sans-serif;font-size:medium;margin:0px">
<font face="Calibri,sans-serif" size="2"><span style="font-size:11pt"> </span></font></div>
<div style="font-family:"Segoe UI",Helvetica,Arial,sans-serif;font-size:medium;margin:0px">
<font face="Calibri,sans-serif" size="2"><span style="font-size:11pt">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-color:rgb(255,255,255)">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></font></div>
<div style="font-family:"Segoe UI",Helvetica,Arial,sans-serif;font-size:medium;margin:0px">
<font face="Calibri,sans-serif" size="2"><span style="font-size:11pt"><br>
</span></font></div>
<div style="margin:0px">
<div style="margin:0px"><font face="Calibri, sans-serif"><span style="font-size:14.6667px">Thank you!</span></font></div>
<div style="margin:0px"><font face="Calibri, sans-serif"><span style="font-size:14.6667px"><br>
</span></font></div>
<div style="font-family:"Segoe UI",Helvetica,Arial,sans-serif;font-size:medium;margin:0px">
<font face="Calibri,sans-serif" size="2"><span style="font-size:11pt"><b>Adrienne Pruitt </b><font size="2"><span style="font-size:9pt">| Collections Management Archivist</span></font></span></font></div>
<div style="font-family:"Segoe UI",Helvetica,Arial,sans-serif;font-size:medium;margin:0px">
<font face="Calibri,sans-serif" size="2"><span style="font-size:11pt"><font size="2"><span style="font-size:9pt">Digital Collections and Archives</span></font></span></font></div>
<div style="font-family:"Segoe UI",Helvetica,Arial,sans-serif;font-size:medium;margin:0px">
<font face="Calibri,sans-serif" size="2"><span style="font-size:11pt"><font size="2"><span style="font-size:9pt">Tufts University</span></font></span></font></div>
<div style="font-family:"Segoe UI",Helvetica,Arial,sans-serif;font-size:medium;margin:0px">
<font face="Calibri,sans-serif" size="2"><span style="font-size:11pt"><a href="mailto:adrienne.pruitt@tufts.edu" target="_blank"><font size="2"><span style="font-size:9pt"><font color="windowtext">adrienne.pruitt@tufts.edu</font></span></font></a><font size="2"><span style="font-size:9pt"> |</span></font><font size="2"><span style="font-size:9pt;background-color:white">617-627-0957</span></font></span></font></div>
</div>
</div>
</div>
_______________________________________________<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=" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="m_8420549641201364889gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div><div><div><div><span><font color="#888888">Chris Mayo<br></font></span></div><span><font color="#888888">Digital Production Librarian<br></font></span></div><span><font color="#888888">Thomas P. O'Neill, Jr. Library<br></font></span></div><span><font color="#888888">Boston College<br></font></span></div><span><font color="#888888"></font></span></div><span><font color="#888888"><a href="mailto:chris.mayo@bc.edu" target="_blank">chris.mayo@bc.edu</a><br></font></span></div></div></div></div></div></div></div></div>
_______________________________________________<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=" rel="noreferrer" 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><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Rachel Searcy<br>Accessioning Archivist, Archival Collections Management<br><div><span style="font-size:12.8000001907349px">New York University Libraries</span><br></div><div><a value="+12129982631">212.998.2539</a> | <a href="mailto:rachel.searcy@nyu.edu" target="_blank">rachel.searcy@nyu.edu</a> <br></div></div></div></div></div></div>