Digital object display in ArcLight - known issues

[dinahhandel]

This ticket is intended to document various known issues with digital object display in ArcLight, primarily due to the way digital objects have been created in ArchivesSpace, or are presented in EAD taken from OAC.

• Digital objects are linked to a SearchWorks digital collection at the collection level, in the front-matter of the finding aid. This results in ArcLight detecting digital content for the collection, but unless the user notices the link in the font matter of the finding aid, they will not find it elsewhere in the collection. Example: https://sul-arclight-demo.stanford.edu/catalog/m1994-xml
• Digital objects are linked to a SearchWorks digital collection at the component level. This results in ArcLight detecting digital content for the collection, but it does not render a viewer in the ArcLight interface, and instead presents the user with a link. Examples: https://sul-arclight-prod.stanford.edu/catalog/m2856-xml_aspace_ece6e4e8a25b1165eb42a02971ce01bc and https://sul-arclight-prod.stanford.edu/catalog/m2468-xml_aspace_ac4ab867028a31ea41ce5e0e702c7b82
• Multiple digital objects are associated with one component. This results in ArcLight detecting one of the digital objects and rendering the viewer, but the additional digital objects appear as links, either to a PURL or SearchWorks. Example: https://sul-arclight-demo.stanford.edu/catalog/ars0213_aspace_6ee1e2b13b8c7a10784f1f01411960b6. In some cases, digital object links are duplicative, and/or lead to defunct or broken services, such as SUL streaming. Example: https://sul-arclight-prod.stanford.edu/catalog/sc0889-xml_ref515
• Some digital objects are present/managed in OAC and follow a different form. See Evaluate status of digital objects in OAC vs. ArchivesSpace  #377 for more information.

During the 2023Q4 prototyping work cycle, @marlo-longley conducted reporting on digital objects in ArchivesSpace. Results documented in ASpace Digital Object Inventory (staging) as well as in #377