[Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results

Custer, Mark mark.custer at yale.edu
Thu Aug 2 11:00:29 EDT 2018

Hi Adrien,

Right now, the logic for this is the same in the staff interface as it is in the public interface.  If the record is a resource, and if that resource record has a Finding Aid Filing Fitle, then the filing title is what's used for sorting.  If there's no filing title, then the resource title is used (not the finding aid title; and I assume that decision was made when ASpace was created since often the finding aid title proper will have things like "Guide to the..." or "Inventory of" etc. at the very beginning).

Here's where that logic happens in the indexer:


I hope that helps (and I hope the bit about the indexer above is correct, but I'm pretty sure that it is).  But if you put the title as you want it to be sorted in the "finding aid filing title" in the staff interface, then you should be all set.  For instance, the "Bradford Edward Ableson Papers" sorts before "Accelerator Laboratories, Yale University, photographs" in our instance  because we have the following recorded in the Finding Aid Filling Title in the staff interface:  "Ableson (Bradford Edward) Papers"

Also, I agree that the report that Eve shared looks great!!!


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien
Sent: Thursday, 02 August, 2018 10:29 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results

Hi Eve,

Congratulations, this looks great!

A question: your collections browse list is alphabetical by something other than the first word of the title that's listed, creator last name, for instance. What field are you sorting this from?

At Harvard, we're currently browsing collections using the first word of the collection title, which is not ideal. We'd prefer to sort by finding aid title, but I've been told this field is not sortable in the core code.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Neiger, Eve
Sent: Wednesday, August 01, 2018 4:05 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results

Dear ArchivesSpace User Group Members:

The Yale University Library ASpace Public User Interface (PUI) Implementation Team has completed pre-launch usability testing work on our customized PUI, now called Archives at Yale. Over the last year, our team has been preparing for the launch of our ASpace PUI and a move from the Yale Finding Aid Database (YFAD).<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__drs.library.yale.edu_fedoragsearch_rest%26d%3DDwMFAg%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Do7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU%26m%3DylCmqQ0O-8R8Z5jgU_-vjyMALIZcGx3tlGS1iRf0ZZw%26s%3DEbFeLEgJ_wFbR1Ja7A_UlzKJpPDHMHOt2aZOVzJtOl4%26e%3D&data=02%7C01%7Cmark.custer%40yale.edu%7C55c0eeda5ec04170817308d5f88445be%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636688169353898109&sdata=fc%2FunjYJpi8dn2%2BCyS3CiJlzehISoQurnm762VUJ6rc%3D&reserved=0> In order to identify and prioritize needed changes and customizations to the out-of-the-box PUI, we ran two rounds of usability testing.

The first round of testing took place in February 2018, followed by an analysis and report. Based on this analysis, we customized our PUI to better match users' mental models, eliminate usability and accessibility issues, and facilitate more accurate searching. During our first round of testing, our Aeon integration for material requesting was not ready so we could not asses usability for requesting at that time. By the time we finished major customizations, the Aeon integration was ready and we ran a second round of testing in June 2018 focused on requesting and the new changes.

We compiled the results from both rounds of usability testing in a report (with an addendum for the second round of testing) and are proud to share it with you now.

You view a copy of our report here: https://drive.google.com/file/d/1yB8ejKvfSokOMZnWn6k8MjL0CYA6WKkq/view?usp=sharing<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__drive.google.com_file_d_1yB8ejKvfSokOMZnWn6k8MjL0CYA6WKkq_view-3Fusp-3Dsharing%26d%3DDwMFAg%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Do7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU%26m%3DylCmqQ0O-8R8Z5jgU_-vjyMALIZcGx3tlGS1iRf0ZZw%26s%3DgrNFeV_E3VHz83XuUpMY3Q84oKgIw4zjEYYB_fRTA3I%26e%3D&data=02%7C01%7Cmark.custer%40yale.edu%7C55c0eeda5ec04170817308d5f88445be%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636688169353908109&sdata=wDs5ogJbzTnPVyXrbLX6yv1eznx5cMaUZXlyhVDs6Q0%3D&reserved=0>
We've also compiled screenshots of our PUI pre-customization for reference: https://drive.google.com/open?id=1lDMTrXSKp4qzujdCzwhu-PzomyL0KAlH<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__drive.google.com_open-3Fid-3D1lDMTrXSKp4qzujdCzwhu-2DPzomyL0KAlH%26d%3DDwMFAg%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Do7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU%26m%3DylCmqQ0O-8R8Z5jgU_-vjyMALIZcGx3tlGS1iRf0ZZw%26s%3D7eTyX8pwkCAcsXQKjEsqQvxo7Cp4MFnPsQjgqPUgUKQ%26e%3D&data=02%7C01%7Cmark.custer%40yale.edu%7C55c0eeda5ec04170817308d5f88445be%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636688169353918123&sdata=6ytaWPyB9J5%2BC%2F1Vcy6UsZCutjN5WVfKnhlHOeUytlM%3D&reserved=0>

And finally, you can see the results of our customizations and the most current version of Archives at Yale (our PUI) here: https://puitestarchivesspace.library.yale.edu/<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__puitestarchivesspace.library.yale.edu_%26d%3DDwMFAg%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Do7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU%26m%3DylCmqQ0O-8R8Z5jgU_-vjyMALIZcGx3tlGS1iRf0ZZw%26s%3DiRqskp189LG1GCTB1pV7exJ3Nb5On6_7o1PJaVBmH-E%26e%3D&data=02%7C01%7Cmark.custer%40yale.edu%7C55c0eeda5ec04170817308d5f88445be%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636688169353918123&sdata=QgmaLNXt%2Fc9BPspLjJdtdhFgxuy1348xCXyNLrDjihc%3D&reserved=0>
*Please note, this is a TEST version or our PUI and may not include up-to-date collection information.

We are happy to answer any questions you have about our usability testing process, analysis, and results. Feel free to reach out to me at eve.neiger at yale.edu<mailto:eve.neiger at yale.edu>.


Eve Neiger, on behalf of the Yale University Library ArchivesSpace Public User Interface Implementation Team, Usability and Accessibility Workgroup

Eve Neiger
Beinecke Rare Book and Manuscript Library
Yale University
203.432.9027 - eve.neiger at yale.edu<mailto:eve.neiger at yale.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180802/a3b23921/attachment.html>

More information about the Archivesspace_Users_Group mailing list