<div dir="ltr"><span id="gmail-docs-internal-guid-a977d79a-7fff-06b0-9e2d-8151391663d2"><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 Robin,</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">We wanted to provide some comments to this proposal for enhancements to ArchivesSpace’s container management functionality. We’d like to thank Harvard for their efforts to put this together to make ArchivesSpace a more useful system for the broader community. We are also a large, multi-repository institution with a single ArchivesSpace instance, and have encountered many of the challenges outlined in this document, although we do operate slightly differently (for example, our locations are shared across our repositories to make the best use of the space we have).</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">We too have found it difficult to browse, filter, and sort through our large number of location records, especially when linking top containers to locations, and support the improvements specified in this document to more efficiently perform these tasks. We would appreciate the ability to return to an existing top container search, but would not want to sacrifice overall system performance for this feature. While the ability to merge locations would be useful in cleaning up obsolete or duplicate locations, we wonder if the logic required to create this functionality might be more complicated than other merging in the system, as there are currently measures in place to ensure that locations cannot be deleted while holdings are linked to them. We think this logic should remain in place to prevent deleting important data.</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">We might not use many of the proposed enhancements (e.g., barcodes for container children, repositories for container profiles) but as long as they are optional and unobtrusive to users who do not employ them, we do not have strong feelings. We do have concerns about the proposal to add a Note field to the Top Container record, especially without a compelling use case to justify its inclusion, as there is such a high likelihood of this field being misused to record information about the </span><span style="font-size:12pt;font-family:Cambria,serif;color:rgb(0,0,0);background-color:transparent;font-style:italic;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">contents </span><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">of a box</span><span style="font-size:12pt;font-family:Cambria,serif;color:rgb(0,0,0);background-color:transparent;font-style:italic;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"> </span><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 opposed to the container itself) more appropriate for specific EAD fields. It reminds us of boxes that have labels with crucial information about the materials inside that is not documented anywhere else, and we wouldn’t want to encourage that type of practice. If there are compelling use cases for this field, we’d prefer values to be controlled so that they can be structured, queried, and used somewhat consistently.</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">Again, thank you for developing this proposal and continuing the conversation. We’re eager to see how this work continues.</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">Best wishes,</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">Rachel</span></p></span></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Dec 10, 2019 at 1:19 PM Wendler, Robin King <<a href="mailto:robin_wendler@harvard.edu">robin_wendler@harvard.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 lang="EN-US">
<div class="gmail-m_4334384107617403335WordSection1">
<p class="gmail-m_4334384107617403335xxmsonormal">Dear ArchivesSpace Community,<u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal" style="text-indent:0.5in">The Harvard Library has been reviewing container and location management functionality in ArchivesSpace and we are proposing to make enhancements to this functionality that we would like to contribute to the core
code. With these enhancements, we hope to make finding, viewing, and updating information related to containers and locations in the staff interface more efficient and effective.
<u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal" style="text-indent:0.5in"> <u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal" style="text-indent:0.5in">Some of you may remember a proposal we distributed this time last year. A variety of factors delayed the work, so we have significantly revised the proposal based on the valuable feedback provided by the ArchivesSpace
community and informed by Harvard archivists’ increasing experience with container management in ArchivesSpace. Some proposals have been removed, while others have been added or altered.
<u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal"> <u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">Additions include<u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="gmail-m_4334384107617403335xxmsonormal">Return to Top Container search results from viewing an individual Top Container record<u></u><u></u></li><li class="gmail-m_4334384107617403335xxmsonormal">Bulk or batch function to create new Top Containers, associate existing Locations with them, and link them to multiple existing archival objects.<u></u><u></u></li><li class="gmail-m_4334384107617403335xxmsonormal">Bulk operation to delete barcodes from Top Containers<u></u><u></u></li><li class="gmail-m_4334384107617403335xxmsonormal">File-upload function to add Locations to Top Containers<u></u><u></u></li><li class="gmail-m_4334384107617403335xxmsonormal">Ability to merge Location records<u></u><u></u></li></ul>
<p class="gmail-m_4334384107617403335xxmsonormal"> <u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">The most significant changes to previous proposals include the following:<u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="gmail-m_4334384107617403335xxmsonormal">The proposed additional indicator fields and ILS Bibliographic Record ID field in Top Containers have been removed.<u></u><u></u></li><li class="gmail-m_4334384107617403335xxmsonormal">The proposed Note field and Inactive checkbox for Locations, along with all functionality associated with inactive status, have been removed.<u></u><u></u></li><li class="gmail-m_4334384107617403335xxmsonormal">Automatic scoping of Container Profiles, Locations, and Location Profiles by repository appears to be too complex, given the community request to make repositories repeatable and the desire for it to be
an installation configuration option. In lieu of that, the revised proposal adds a repeatable, optional repository field to container profiles and adds a facet for filtering by repository to browse results for Container Profiles and Locations.<u></u><u></u></li><li class="gmail-m_4334384107617403335xxmsonormal">Proposed functionality around Location status has been removed<u></u><u></u></li></ul>
<p class="gmail-m_4334384107617403335xxmsonormal"> <u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">The revised draft proposal is attached to this email and we are asking for community review and feedback. The proposal includes the rationale for the changes, a list of database fields to be added, user stories describing the specific
changes we are proposing, and mockups of the related updates to the staff interface. Please note that the proposal represents a superset of the work we may be able to complete in the next couple of months, and that not all the proposed changes will be addressed
at this time. Another caveat: some of the desiderata require further technical design that will determine what approach will be taken. These will be investigated in consultation with Lyrasis ArchivesSpace staff.<u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal"> <u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">If you have questions or feedback, please email me at <a href="mailto:robin_wendler@harvard.edu" target="_blank">
robin_wendler@harvard.edu</a>. <b>We will be accepting comments through Wednesday, December 18, 2019.</b><u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal"> <u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">We look forward to receiving community input. <u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal"> <u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">Best,<u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">Robin<u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal"> <u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">Robin Wendler<u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">Library Technology Services<u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">Harvard University<u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">90 Mt. Auburn St.<u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">Cambridge, MA 02138<u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">617-998-5457<u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal">617-495-3724<u></u><u></u></p>
<p class="gmail-m_4334384107617403335xxmsonormal"><a href="mailto:r_wendler@harvard.edu" target="_blank">r_wendler@harvard.edu</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Robin Wendler<u></u><u></u></p>
<p class="MsoNormal">Library Technology Services<u></u><u></u></p>
<p class="MsoNormal">Harvard University<u></u><u></u></p>
<p class="MsoNormal">90 Mt. Auburn St.<u></u><u></u></p>
<p class="MsoNormal">Cambridge, MA 02138<u></u><u></u></p>
<p class="MsoNormal">617-998-5457<u></u><u></u></p>
<p class="MsoNormal">617-495-3724<u></u><u></u></p>
<p class="MsoNormal"><a href="mailto:r_wendler@harvard.edu" target="_blank">r_wendler@harvard.edu</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</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=xCPRgg7M_MSTK8m534QQeiXyHPD8UZ765hwtNHj9an0&s=Tqu4WUEA3bqTFcWqfAJWzW-Hd4lnvqlAZ8MT2TWeta4&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=xCPRgg7M_MSTK8m534QQeiXyHPD8UZ765hwtNHj9an0&s=Tqu4WUEA3bqTFcWqfAJWzW-Hd4lnvqlAZ8MT2TWeta4&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>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</div></div></div></div></div></div></div></div></div>