<div dir="ltr"><span id="gmail-docs-internal-guid-83b3c71c-7fff-9757-2035-63739882823e"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:12pt;font-family:Cambria,serif;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Hi Celia,</span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:12pt;font-family:Cambria,serif;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">I think this is a great question, and I’d be curious to hear what other folks are doing.</span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:12pt;font-family:Cambria,serif;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">As a general rule we use container instances to record information about physical materials, and digital objects to record information about born-digital materials or digital surrogates. We track the physical locations of any physical carriers using instances to record the box an item is in, and we use digital objects to record the AIP in our digital repository. At the point of accessioning, we typically have a single archival object with a single digital object to represent the entirety of the born-digital materials for the accession, whereas our arrangement and description activities typically (although not always) result in more granular representation. </span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:12pt;font-family:Cambria,serif;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Alongside this, we also record extent(s) and create or edit descriptive metadata in the accession and resource record to document what we understand about the formats, content, and context of these born-digital materials. Our accessioning workflow includes the creation of an accession record for this particular grouping of materials, as well as the creation or editing of a resource record to represent the collection in its entirety.</span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:12pt;font-family:Cambria,serif;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><br></span></p><p style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:12pt;font-family:Cambria,serif;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">I'd echo Jessica's comment about consistency, and further it by underscoring the importance of documenting your local decisions in service of that. </span><span style="background-color:transparent;color:rgb(0,0,0);font-family:Cambria,serif;font-size:12pt;white-space:pre-wrap">Your question raises the need for flexible and supportive best practices for accessioning so that archivists can adapt them locally to address issues like scale, infrastructure, specific tools, concrete workflows, and resourcing. It is extremely encouraging that SAA has approved a three-year Best Practices Working Group for Accessioning, a group whose work is currently underway and is paying explicit attention to the particular needs of born-digital materials.</span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:12pt;font-family:Cambria,serif;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Looking forward to hearing what others do as well.</span></p></span><br class="gmail-Apple-interchange-newline"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 4, 2022 at 9:27 AM Jessica Steytler <<a href="mailto:jasteytler@minlib.net">jasteytler@minlib.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Seems likely that either is good, as long as one is consistent, right?<div>I can picture myself putting in born-digital content as accessions in my near future, but I haven't done it yet, so I just tried it out and my instinct is for Digital Object-- its ID is its location/URL, which totally fits in my brain as opposed to an actual object. </div><div><br></div><div>Jessica</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 31, 2022 at 10:50 AM Celia Caust-Ellenbogen <<a href="mailto:ccauste1@swarthmore.edu" target="_blank">ccauste1@swarthmore.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi folks,<div><br>We're revamping our workflow for accessioning born-digital materials, and we'd love advice from folks using ASpace for this. </div><div><br></div><div>In particular, we're stuck on questions about tracking locations for accessioning unprocessed born-digital materials in cloud storage...should we use instances or DAOs?</div><div><br></div><div>If you have opinions on this and would be willing to discuss/advise, I would be grateful to hear from you!</div><div>Celia<br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><font size="1">Celia Caust-Ellenbogen (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.swarthmore.edu_lgbtq_gender-2Dpronouns&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=g9uM2eSEUu_t0KHTdKZ1DdTofCaAXZTMz9TGtERbRfuWmIimxIWXviSEzzXbP-q1&s=0M8XcM74uCfgxKkZrFVozor3JQ8uJp3sgNildbZBdkI&e=" target="_blank">she/her/hers</a>) (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.name-2Dcoach.com_celia-2Dcaust-2Dellenbogen&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=g9uM2eSEUu_t0KHTdKZ1DdTofCaAXZTMz9TGtERbRfuWmIimxIWXviSEzzXbP-q1&s=NVzWfSPa8qkWL5_gS3wvrQeSBoSzY7Cx8zbdp-_VXV8&e=" target="_blank">pronounce my name</a>)</font><div><font size="1"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__swarthmore.edu_friends-2Dhistorical-2Dlibrary&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=g9uM2eSEUu_t0KHTdKZ1DdTofCaAXZTMz9TGtERbRfuWmIimxIWXviSEzzXbP-q1&s=q7WQIhco0tbTJVTZGKyZVk_SdrYrTEh_T3ORheXbxgk&e=" target="_blank">Friends Historical Library of Swarthmore College</a></font></div><div><a href="mailto:ccauste1@swarthmore.edu" style="font-size:x-small" target="_blank">ccauste1@swarthmore.edu</a></div></div></div></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=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=g9uM2eSEUu_t0KHTdKZ1DdTofCaAXZTMz9TGtERbRfuWmIimxIWXviSEzzXbP-q1&s=K-Q8xtqK34FQdkF0INx2DqF0pzxtf3EeKRssheaj9ww&e=" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Jessica Steytler | <i>she/her</i> <font size="1">(<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.mypronouns.org_what-2Dand-2Dwhy&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=g9uM2eSEUu_t0KHTdKZ1DdTofCaAXZTMz9TGtERbRfuWmIimxIWXviSEzzXbP-q1&s=0OekFpgH27Lw-CKqMVAO5NDXrN6YBRLizw1ABthnrJU&e=" target="_blank">why does this matter?</a>)</font></div><div>Reference - Special Collections</div><div>Public Library of Brookline</div><div>617-730-2375</div><div><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__brooklinelibrary.org&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=g9uM2eSEUu_t0KHTdKZ1DdTofCaAXZTMz9TGtERbRfuWmIimxIWXviSEzzXbP-q1&s=bNxstr9hIZtDt_y3BDCrBP90pbJJ5-LRTqN8RYgmRs0&e=" target="_blank">http://brooklinelibrary.org</a></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=g9uM2eSEUu_t0KHTdKZ1DdTofCaAXZTMz9TGtERbRfuWmIimxIWXviSEzzXbP-q1&s=K-Q8xtqK34FQdkF0INx2DqF0pzxtf3EeKRssheaj9ww&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=g9uM2eSEUu_t0KHTdKZ1DdTofCaAXZTMz9TGtERbRfuWmIimxIWXviSEzzXbP-q1&s=K-Q8xtqK34FQdkF0INx2DqF0pzxtf3EeKRssheaj9ww&e=</a> <br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Rachel Searcy<br>Accessioning Archivist, Archival Collections Management<br><div><span style="font-size:12.8px">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>My pronouns are she/her/hers</div></div></div></div></div></div></div></div></div></div></div>