ArchivesSpace Member Forum 2018

Not sure if this has been discussed somewhere already, but it's something we've been doing for a while and haven't really mentioned. Someone asked about Alma integrations on the ASpace list recently and there was a response about the University of Denver's Alma plugin. That is useful, but we are doing something that I think is even easier and does not require a plugin. Better still, the finding aid record gets into Primo and is full text searchable, even though the entire finding aid doesn't actually display in the record. Alma isn't required, the record shows up in Primo, and ArchivesSpace remains the system of record for finding aids. I'd like to go over this workflow as a lightning talk.

Seton Hall recently used the new OAI functionality of Archivesspace to integrate Archivesspace records into the discovery layer of the university libraries, namely EDS, Ebsco's discovery layer. This will make archival collections much easier to find for the majority of library users, who simply search the library catalog in their research rather than going to the Special Collections page and finding Archivesspace. However, there are some problems: notably, duplicate records with collections that had previously been cataloged on a piecemeal basis, and folder records that made no sense out of context. Also, certain fields that were automatically imported by the harvester designed by Ebsco are not useful in a library catalog. I will discuss our process and our plans to improve the end result.

We would like to present a case study of Yale University Library’s experience using DIY usability testing to identify and prioritize customizations to the out-of-the-box ArchivesSpace Public User Interface (PUI). In preparing Yale University Library’s PUI for launch, an implementation team was formed to identify custom settings and enhancements to meet user needs. Replacing the current Yale Finding Aid Database (YFAD), the PUI presents archival description in a very different way than Yale’s current, static, document-like online finding aids. Yale staff wanted the PUI to provide the same service as YFAD and improve on that service, all while creating a smooth transition between discovery platforms. However, an open source software designed to be be customized in-house and an internal lack of IT developer resources created challenges. To set priorities and make decisions about visuals, data display, site structure, and other enhancements, we conducted qualitative usability tests with users from our target audiences and tested the site for WCAG 2.0 compliance. Test results were compiled in a report with recommendations to address user confusions and frustrations. As is often the case, usability and accessibility issues overlapped, providing a stronger argument for key changes. After analyzing user feedback, we prioritized customizations and consulted with developers at Lyrasis to create a customized Yale PUI that meets our users’ needs while also contributing several enhancements to the PUI core code. Through iterative testing and prioritization, we’ve created a scalable method for capturing and incorporating user needs into our PUI customization.