<div dir="ltr">Hi Anna,<br><div><br></div><div>There was not an issue filed, but you inspired me to file my first JIRA issue! Hopefully, I filled out everything correctly, but here is the ticket if you or anyone else wants to add any comments:</div><div><a href="https://archivesspace.atlassian.net/browse/ANW-1488">https://archivesspace.atlassian.net/browse/ANW-1488</a><br></div><div><br></div><div>Thanks!</div><div>Olivia</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 2, 2022 at 4:04 PM Anna Haywood <<a href="mailto:ahaywood@cca.qc.ca">ahaywood@cca.qc.ca</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="FR-CA" style="overflow-wrap: break-word;">
<div class="gmail-m_-332761454677249289WordSection1">
<p class="MsoNormal"><span>Hello Olivia, <u></u>
<u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">This is a very late reply but I would like to second this idea. Our institution would be very interested in having a generic note field on top containers.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">When we create accession records, we attach container instances to the accession record to keep track of which unprocessed boxes came with which accession. Rather than link to an external
inventory, or have to create component records for unprocessed materials, we would prefer to be able to give a brief note about the container’s contents in this field.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Please let me know if you open a development ticket because I would strongly support it.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Best,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Anna<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p style="font-size:8pt;font-family:ARIAL">---<br><br><strong>Anna
Haywood<br></strong>Archiviste<br>Archivist<br><br><span style="font-size:8pt"><strong>Centre Canadien d'Architecture<br>Canadian Centre
for Architecture</strong><br></span>1920, rue Baile, Montréal, Québec, Canada,
H3H 2S6<br>+1 5149397001x1368<br><a title="" style="text-decoration:none;color:rgb(0,0,0)" href="https://www.cca.qc.ca/fr/?utm_source=fr_email_signature&utm_medium=email" target="_blank">cca.qc.ca</a><br><a title="" href="https://www.twitter.com/ccawire" target="_blank">Twitter</a> | <a title="" href="https://www.instagram.com/canadiancentreforarchitecture/" target="_blank">Instagram</a> |
<a title="" href="https://www.facebook.com/cca.conversation" target="_blank">Facebook</a> | <a title="" href="https://www.youtube.com/user/CCAchannel" target="_blank">YouTube</a></p>
<p style="font-size:8pt;font-family:ARIAL"><a title="" href="https://bit.ly/3ESiRoN" target="_blank">Qu'est-ce qui vous pousse à privilégier une
caractéristique plutôt qu'une autre pour décrire un objet?</a><br><a title="" href="https://bit.ly/3yvQquM" target="_blank">What makes you pick one characteristic over
another to describe an object?</a></p>
<p style="font-size:8pt;font-family:ARIAL"><a title="" href="https://www.cca.qc.ca/fr/?go=enews&utm_source=fr_email_signature&utm_medium=email" target="_blank">Inscrivez-vous</a>
pour recevoir de nos nouvelles.<br><a title="" href="https://www.cca.qc.ca/en/?go=enews&utm_source=en_email_signature&utm_medium=email" target="_blank">Sign
up</a> to get news from us.</p><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
<b>On Behalf Of </b>Olivia S Solis<br>
<b>Sent:</b> Monday, December 13, 2021 1:13 PM<br>
<b>To:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Subject:</b> [Archivesspace_Users_Group] Generic top container note?<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Hey all,<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I was wondering if any other institutions out there had an interest in a field that we have consistently found a need for: a generic note for staff attached to top container records. Reasons have included:<u></u><u></u></p>
</div>
<div>
<ul type="disc">
<li class="MsoNormal">
We renamed a box. Because boxes may be part of citations or referenced in numerous places in internal documentation, staff sometimes goes to absurd lengths to keep an old box number when it is no longer relevant or the box really should be renamed. Having the
old box # in a note that is indexed gets rid of that problem as there is an immediately obvious place to document the change. Staff and researchers often look for a box number they've found in citations and notes. Keeping this information in a note on the
container record would allow us to locate the correct container through a key-word search.<u></u><u></u></li><li class="MsoNormal">
We merged two boxes into one.<u></u><u></u></li><li class="MsoNormal">
We want to document the space left in a box and ASpace currently allows no way to do that.<u></u><u></u></li><li class="MsoNormal">
The box has a nonstandard size (no container profile yet)<u></u><u></u></li><li class="MsoNormal">
The box needs some upkeep (new label, new container, it's missing a lid)<u></u><u></u></li><li class="MsoNormal">
We can't find a box. It's happened. We want to document all the places we've looked<u></u><u></u></li><li class="MsoNormal">
Other internal notes about the box's status, condition, barcode or indicator or history, restriction status.<u></u><u></u></li></ul>
<div>
<p class="MsoNormal">It seems like ASpace wants us to document information about top containers in other places including Processing Notes attached to specific archival objects/resource records/accessions, assessments, location notes. Location notes sometimes
could work, but we have limited staff time and can't update numerous records (all the archival objects/collections attached to a box or assessments attached to AOs/collections) to document a single change.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<div>
<p class="MsoNormal">A generic note attached to top containers would solve a lot of problems for us. If you have encountered any similar issue, how have you approached them in ASpace?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Olivia<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt;color:black">Olivia Solis, MSIS (she/her)</span><span style="font-size:9.5pt"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt;color:black">Metadata Coordinator</span><span style="font-size:9.5pt"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt;color:black">Dolph Briscoe Center for American History</span><span style="font-size:9.5pt"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt;color:black">The University of Texas at Austin</span><span style="font-size:9.5pt"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt;color:black">2300 Red River St. Stop D1100<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt;color:black">Austin TX, 78712-1426</span><span style="font-size:9.5pt"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt;color:black">(512) 232-8013</span><span style="font-size:9.5pt;color:rgb(136,136,136)"><u></u><u></u></span></p>
</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="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" 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" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="font-size:12.8px"><font color="#000000">Olivia Solis, MSIS (she/her)</font></div><div style="font-size:12.8px"><font color="#000000">Metadata Coordinator</font></div><div style="font-size:12.8px"><font color="#000000">Dolph Briscoe Center for American History</font></div><div style="font-size:12.8px"><font color="#000000">The University of Texas at Austin</font></div><div style="font-size:12.8px"><font color="#000000">2300 Red River St. Stop D1100</font></div><div style="font-size:12.8px"><font color="#000000">Austin TX, 78712-1426</font></div><div style="color:rgb(136,136,136);font-size:12.8px"><span style="color:rgb(0,0,0);font-size:12.8px">(512) 232-8013</span></div></div></div></div></div></div></div>