<div dir="ltr"><span id="gmail-docs-internal-guid-d3ebf287-7fff-44be-bc5d-2fce43ab00e8"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Hey there ASpace list,</span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">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></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Here are the two approaches we’ve taken. I see pluses and minuses: </span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">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></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><span style="border:none;display:inline-block;overflow:hidden;width:631px;height:77px"><img src="https://lh3.googleusercontent.com/h1gOnm4gLUMsOkM7ShuPikZJMpY8ZwsQAj-gVGJws5K6m75MIa8qjzUyHfMiGRvcAX4ELJg0GE2T5Zk1lPIUTrkuRkTkc96fU47C0ONY87t2XoRh3K48xQ1ieyjZ_jBOEf8TShj9" width="738.7317073170731" height="77" style="margin-top: 0px;"></span></span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">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></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><span style="border:none;display:inline-block;overflow:hidden;width:624px;height:65px"><img src="https://lh6.googleusercontent.com/4lxCTd6c0IIlfWYIXOjWgGv38DLlzakRsLwBQjjyso6KB6yTm3YaydBDG8Ask6SX1Zsu39SiVua3y0TTEce0zGURxlfT1hrJhKaYt8tAfjljaATqQR2BsgcgB7SEffpYIFIuGlBr" width="624" height="65" style="margin-left: 0px; margin-top: 0px;"></span></span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">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></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Thanks for your help!</span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Amy</span></p></span><br class="gmail-Apple-interchange-newline"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>--------------------<br></div><div dir="ltr">Amy Braitsch (pronouns: she/her/hers)</div><div dir="ltr">Head of Archives, Burns Library, Boston College, <a href="mailto:amy.braitsch@bc.edu" target="_blank">amy.braitsch@bc.edu</a></div></div></div></div></div></div></div></div></div></div>