Bug #13583

Container information no longer appearing in generated finding aids

Added by Dan Gillean 2 months ago.

Status:NewStart date:11/12/2021
Priority:MediumDue date:
Assignee:-% Done:


Category:Finding aids
Target version:-
Google Code Legacy ID: Tested version:2.6, 2.7
Sponsored:No Requires documentation:No


First reported in the user forum, 2021-11-12: https://groups.google.com/g/ica-atom-users/c/FDA7NvozMFc/m/Kz-CMLNVAAAJ

In Issue #10591, we made a number of improvements to the finding aid formatting, normalizing a few things, reordering some elements, and limiting the size of the table of contents. Additionally, physical storage information (which was previously shown in the table-based output for lower-level descriptions in the Inventory summary) was moved from the inventory table and into the body output of each lower-level record.

However, while previously container information was included in the output of both finding aid types (via EAD element <container>), now only location information (<physloc>) is being included. This change was introduced in AtoM version 2.6.0. with #10591.

I have reviewed the conversations with the original development sponsor (this began as a community pull request from Dalhousie University, and was completed by Artefactual), and I can find no specific intention to remove this information.

AtoM has a method for users to exclude any physical storage information from generated finding aids already - user can:

  • Hide the storage information via the Visible Elements module
  • Set finding aids to generate as a public user

When these two things are done, no physical storage information (either physloc or container) should appear in the resulting finding aids. See:

Ultimately, including only physloc data is less useful, since many containers may share the same general location. Ideally, both physloc and container data should appear in the finding aid, and enabling the Visible elements module exclusion for public-generated finding aids should hide both physloc and container info.

To reproduce

  • Navigate to Admin > Visible elements and ensure that physical storage information is NOT hidden from public users (i.e. is checked in Visible elements)
  • Find or create a hierarchical description that includes physical storage data - ensure that lower level records include both location and container information, or else add some
  • Delete any existing finding aid (to ensure you are seeing the latest version)
  • Generate a finding aid

Resulting error

  • No container information is included

Expected result

  • Both location and container information are included when AtoM is configured to include physical storage information in finding aids.

Ideally, this information would appear concatenated together - the @id and @parent attributes in the relevant elements can be used to relate them when there are multiple containers/locations. Example EAD output:

<physloc id="physloc0012">Processing Room B</physloc>
<container type="shelf" parent="physloc0012"> DD-10/11/12/13 </container>

Ideal finding aid output:

Storage information: [physloc data] - [container data]

Acceptable finding aid layout: having container and location information listed separately but following each other in the finding aid layout

Hard requirement: That hiding physical storage information in visible elements/the finding aid hides BOTH elements if displayed separately

Related issues

Related to Access to Memory (AtoM) - Feature #10591: Update finding aid XSLTs with formatting improvements Verified 11/21/2016


#1 Updated by Dan Gillean 2 months ago

  • Related to Feature #10591: Update finding aid XSLTs with formatting improvements added

Also available in: Atom PDF