[Archivesspace_Users_Group] Approach to describing single items

Cory Nimer cory_nimer at byu.edu
Thu Feb 3 15:35:57 EST 2022


We use the Option 1 here, though we also have had some concerns with the PUI thumbnail display at this level. Looking ahead, we are hoping that the display issues will be fixed with the 3.2.0 release--the release candidate notes reference ANW-810 (https://archivesspace.atlassian.net/browse/ANW-810), which seems to cover this use case. There are also some proposed fixes for this issue in the draft specification for ANW-1209 (https://archivesspace.atlassian.net/browse/ANW-1209), which was under discussion by the Development Prioritization Subteam in their meeting on Tuesday (https://archivesspace.atlassian.net/wiki/spaces/AC/pages/3022716936/2022-02-01+Meeting+notes).


Cory Nimer
University Archivist
Brigham Young University

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Amy Braitsch
Sent: Thursday, February 3, 2022 8:20 AM
To: Archivesspace_Users_Group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Approach to describing single items

Hey there ASpace list,

At BC we're working toward implementing the PUI. To get there we've remediated a lot of legacy data and data practice. An area we haven't handled yet is what to do with single item resources (e.g. a diary). We've been inconsistent and need to settle on one approach. I'd like to know what you've found to be the best approach and why.

Here are the two approaches we’ve taken. I see pluses and minuses:

Option 1: Resource without archival objects, with instances/digital objects associated at the collection level. This makes logical sense, but the PUI displays these containers/digital objects differently than on collections with instances on the archival objects. The biggest difference in the PUI is that thumbnails are omitted from the digital objects when they’re at this level. On the staff side, the collection-level resource lacks the ref ID and CUI field, which we use as part of our digital object file naming convention.


Option 2: Resource with a child archival object (repeating the title of the parent), with instances/digital objects associated with the AO. This seems like redundant record-keeping. It requires more researcher clicks in the PUI, but the display of the instances are consistent with other collections. On the staff side, the ref ID and CUI are available for use in our digital object workflows.


We rely on ASpace for collection management and description. As we move into using it for discovery as well, I want to be sure that we're following road-tested best practices.

Thanks for your help!


Amy Braitsch (pronouns: she/her/hers)
Head of Archives, Burns Library, Boston College, amy.braitsch at bc.edu<mailto:amy.braitsch at bc.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220203/cd030de3/attachment.html>

More information about the Archivesspace_Users_Group mailing list