[Archivesspace_Users_Group] Generic top container note?

[Olivia S Solis]

Hi Anna,

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:
https://archivesspace.atlassian.net/browse/ANW-1488

Thanks!
Olivia

On Wed, Feb 2, 2022 at 4:04 PM Anna Haywood <ahaywood at cca.qc.ca> wrote:

> Hello Olivia,
>
>
>
> 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.
>
>
>
> 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.
>
>
>
> Please let me know if you open a development ticket because I would
> strongly support it.
>
>
>
> Best,
>
> Anna
>
>
>
> ---
>
>
> *Anna Haywood*Archiviste
> Archivist
>
>
> *Centre Canadien d'ArchitectureCanadian Centre for Architecture*
> 1920, rue Baile, Montréal, Québec, Canada, H3H 2S6
> +1 5149397001x1368
> cca.qc.ca
> <https://www.cca.qc.ca/fr/?utm_source=fr_email_signature&utm_medium=email>
> Twitter <https://www.twitter.com/ccawire> | Instagram
> <https://www.instagram.com/canadiancentreforarchitecture/> | Facebook
> <https://www.facebook.com/cca.conversation> | YouTube
> <https://www.youtube.com/user/CCAchannel>
>
> Qu'est-ce qui vous pousse à privilégier une caractéristique plutôt qu'une
> autre pour décrire un objet? <https://bit.ly/3ESiRoN>
> What makes you pick one characteristic over another to describe an object?
> <https://bit.ly/3yvQquM>
>
> Inscrivez-vous
> <https://www.cca.qc.ca/fr/?go=enews&utm_source=fr_email_signature&utm_medium=email>
> pour recevoir de nos nouvelles.
> Sign up
> <https://www.cca.qc.ca/en/?go=enews&utm_source=en_email_signature&utm_medium=email>
> to get news from us.
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Olivia
> S Solis
> *Sent:* Monday, December 13, 2021 1:13 PM
> *To:* Archivesspace Users Group <
> archivesspace_users_group at lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] Generic top container note?
>
>
>
> Hey all,
>
>
>
> 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:
>
>    - 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.
>    - We merged two boxes into one.
>    - We want to document the space left in a box and ASpace currently
>    allows no way to do that.
>    - The box has a nonstandard size (no container profile yet)
>    - The box needs some upkeep (new label, new container, it's missing a
>    lid)
>    - We can't find a box. It's happened. We want to document all the
>    places we've looked
>    - Other internal notes about the box's status, condition, barcode or
>    indicator or history, restriction status.
>
> 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.
>
>
>
> 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?
>
>
>
> Thanks,
>
> Olivia
>
>
>
> --
>
> Olivia Solis, MSIS (she/her)
>
> Metadata Coordinator
>
> Dolph Briscoe Center for American History
>
> The University of Texas at Austin
>
> 2300 Red River St. Stop D1100
>
> Austin TX, 78712-1426
>
> (512) 232-8013
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Olivia Solis, MSIS (she/her)
Metadata Coordinator
Dolph Briscoe Center for American History
The University of Texas at Austin
2300 Red River St. Stop D1100
Austin TX, 78712-1426
(512) 232-8013
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220207/28896280/attachment-0001.html>