<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
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><!--[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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi Amy,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We use Option 2 and also rely on the CUI for Digital Object IDs and downstream digitization processes.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We used this same pattern in our legacy EAD authoring/discovery system in a component description (<did>…<unitid>) and continued it into aspace.<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">Teleworking M-F 8:00AM – 4:30PM Eastern Time each day until further notice<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>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Cory Nimer <cory_nimer@byu.edu> <br>
<b>Sent:</b> Thursday, February 3, 2022 3:36 PM<br>
<b>To:</b> amy.braitsch@bc.edu; Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> [EXTERNAL] Re: [Archivesspace_Users_Group] Approach to describing single items<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:solid #9C6500 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt">
<p class="MsoNormal" style="line-height:12.0pt;background:#FFEB9C"><span style="font-size:10.0pt;color:#9C6500">CAUTION:</span><span style="font-size:10.0pt;color:black"> This email originated from outside of the organization. Do not click links or open attachments
unless you recognize the sender and are confident the content is safe.<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Amy,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We use the Option 1 here, though we also have had some concerns with the PUI thumbnail display at this level. Looking ahead, we are hoping that the display issues will be fixed with the 3.2.0 release--the release candidate notes reference
ANW-810 (<a href="https://archivesspace.atlassian.net/browse/ANW-810">https://archivesspace.atlassian.net/browse/ANW-810</a>), which seems to cover this use case. There are also some proposed fixes for this issue in the draft specification for ANW-1209 (<a href="https://archivesspace.atlassian.net/browse/ANW-1209">https://archivesspace.atlassian.net/browse/ANW-1209</a>),
which was under discussion by the Development Prioritization Subteam in their meeting on Tuesday (<a href="https://archivesspace.atlassian.net/wiki/spaces/AC/pages/3022716936/2022-02-01+Meeting+notes">https://archivesspace.atlassian.net/wiki/spaces/AC/pages/3022716936/2022-02-01+Meeting+notes</a>).
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cory Nimer<o:p></o:p></p>
<p class="MsoNormal">University Archivist<o:p></o:p></p>
<p class="MsoNormal">Brigham Young University<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<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>Amy Braitsch<br>
<b>Sent:</b> Thursday, February 3, 2022 8:20 AM<br>
<b>To:</b> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<b>Subject:</b> [Archivesspace_Users_Group] Approach to describing single items<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p style="margin:0in"><span style="font-family:"Arial",sans-serif;color:black">Hey there ASpace list,</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in"><span style="font-family:"Arial",sans-serif;color:black">At BC we're working toward implementing the PUI. To get there we've remediated a lot of legacy data and data practice. An area we haven't handled yet is what to do with single item
resources (e.g. a diary). We've been inconsistent and need to settle on one approach. I'd like to know what you've found to be the best approach and why. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in"><span style="font-family:"Arial",sans-serif;color:black">Here are the two approaches we’ve taken. I see pluses and minuses: </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in"><span style="font-family:"Arial",sans-serif;color:black">Option 1: Resource without archival objects, with instances/digital objects associated at the collection level. This makes logical sense, but the PUI displays these containers/digital
objects differently than on collections with instances on the archival objects. The biggest difference in the PUI is that thumbnails are omitted from the digital objects when they’re at this level. On the staff side, the collection-level resource lacks the
ref ID and CUI field, which we use as part of our digital object file naming convention.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in"><span style="font-family:"Arial",sans-serif;color:black;border:none windowtext 1.0pt;padding:0in"><img border="0" width="737" height="77" style="width:7.677in;height:.802in" id="_x0000_i1026" src="https://lh3.googleusercontent.com/h1gOnm4gLUMsOkM7ShuPikZJMpY8ZwsQAj-gVGJws5K6m75MIa8qjzUyHfMiGRvcAX4ELJg0GE2T5Zk1lPIUTrkuRkTkc96fU47C0ONY87t2XoRh3K48xQ1ieyjZ_jBOEf8TShj9"></span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in"><span style="font-family:"Arial",sans-serif;color:black">Option 2: Resource with a child archival object (repeating the title of the parent), with instances/digital objects associated with the AO. This seems like redundant record-keeping.
It requires more researcher clicks in the PUI, but the display of the instances are consistent with other collections. On the staff side, the ref ID and CUI are available for use in our digital object workflows.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in"><span style="font-family:"Arial",sans-serif;color:black;border:none windowtext 1.0pt;padding:0in"><img border="0" width="624" height="65" style="width:6.5in;height:.677in" id="_x0000_i1025" src="https://lh6.googleusercontent.com/4lxCTd6c0IIlfWYIXOjWgGv38DLlzakRsLwBQjjyso6KB6yTm3YaydBDG8Ask6SX1Zsu39SiVua3y0TTEce0zGURxlfT1hrJhKaYt8tAfjljaATqQR2BsgcgB7SEffpYIFIuGlBr"></span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in"><span style="font-family:"Arial",sans-serif;color:black">We rely on ASpace for collection management and description. As we move into using it for discovery as well, I want to be sure that we're following road-tested best practices. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in"><span style="font-family:"Arial",sans-serif;color:black">Thanks for your help!</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-family:"Arial",sans-serif;color:black">Amy</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">--------------------<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Amy Braitsch (pronouns: she/her/hers)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Head of Archives, Burns Library, Boston College, <a href="mailto:amy.braitsch@bc.edu" target="_blank">amy.braitsch@bc.edu</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>