[Archivesspace_Users_Group] Generic top container note?

Olivia S Solis livsolis at utexas.edu
Mon Dec 13 16:08:27 EST 2021

Oh wow, Katie, that is interesting... It is likewise nice to see we are not
alone! Are you maintaining that outside of ASpace or are you developing a
plugin? Given "system" it would seem it's totally separate. If so, does
your system integrate with or is it in communication with ASpace at all?


On Mon, Dec 13, 2021 at 1:19 PM Bowers, Kate A. <kate_bowers at harvard.edu>

> Interesting! All of these are in our specification for our custom
> container management system, which we determined we needed because
> ArchivesSpace could not accommodate them. It’s nice to see our needs were
> not unique.
> Kate
> *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?
> WARNING: Harvard cannot validate this message was sent from an authorized
> system. Please be careful when opening attachments, clicking links, or
> following instructions. For more information, visit the HUIT IT Portal and
> search for SPF.
> ------------------------------
> 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/20211213/caa337c0/attachment.html>

More information about the Archivesspace_Users_Group mailing list