[Archivesspace_Users_Group] Finding Air Filing Title sort [was: Yale Library ASpace PUI Usability Testing Final Report + Results]

Majewski, Steven Dennis (sdm7g) sdm7g at virginia.edu
Thu Aug 2 15:57:39 EDT 2018 

I usually agree with the notion that you shouldn’t try modifying resources directly in MySQL unless you know what you’re doing. 
That’s because, when you’re dealing with linked resources, you need to define some complicated views using multiple JOINs in MySQL to follow those linkages so that parents and children all get updated properly. The backend API resolves these links for you in most cases, so it’s simpler to use the API. 

However, this is one of those cases where you would just be modifying one MySQL resource field based on another in the same record, so no extra link resolution required. Simpler to update in MySQL and then trigger a Solr reindex. ( Because making changed directly in MySQL bypasses the indexer notifications. ) Also a lot more efficient if you’ve got a lot of resources. 

— Steve. 



> On Aug 2, 2018, at 2:56 PM, Custer, Mark <mark.custer at yale.edu> wrote:
> 
> That’s actually a really good use case for using the ASpace API.  The Finding Aid Title field could be moved (or duplicated) in the Filing Title field with a sleek script!
>  
>  
>  
> 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 11:42 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 Mark, 
>  
> Yeah, legacy practice across Harvard was not to use Finding Aid Filing Title, just Finding Aid Title, which was formatted like, “Last Name, First Name. First Name Last Name papers: Guide.”
>  
> But thanks for the link, that might help us develop a solution.
>  
> Best wishes, 
> Adrien
>  
>  
> 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 Custer, Mark
> Sent: Thursday, August 02, 2018 11:00 AM
> To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org <mailto:archivesspace_users_group at lyralists.lyrasis.org>>
> Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results
>  
> 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:
>  
> https://github.com/archivesspace/archivesspace/blob/master/indexer/app/lib/indexer_common.rb#L888-L890 <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__github.com_archivesspace_archivesspace_blob_master_indexer_app_lib_indexer-5Fcommon.rb-23L888-2DL890%26d%3DDwMFAg%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Do7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU%26m%3D_W6Y2-L3MuZlIdndB1sqRCYzyVktoECCp37grV7zXr4%26s%3DHdcHNdb2z4RLjGvE683W6-rwceyV4zfaosHaMmVD1vI%26e%3D&data=02%7C01%7Cmark.custer%40yale.edu%7Ca5e4444d211f40520d1308d5f88fef40%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636688219452628981&sdata=cKQ%2BDVvPCfhSTHdDpQngwtImxOKFkOUwVxHrJ9C7QUM%3D&reserved=0>
>  
> 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!!!
>  
> Mark
>  
>  
>  
>  
> From: archivesspace_users_group-bounces at lyralists.lyrasis.org <mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto: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 <mailto: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.
>  
> Thanks, 
> Adrien
>  
> 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%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttp-2D3A-5F-5Fdrs.library.yale.edu-5Ffedoragsearch-5Frest-2526d-253DDwMFAg-2526c-253DWO-2DRGvefibhHBZq3fL85hQ-2526r-253Do7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU-2526m-253DylCmqQ0O-2D8R8Z5jgU-5F-2DvjyMALIZcGx3tlGS1iRf0ZZw-2526s-253DEbFeLEgJ-5FwFbR1Ja7A-5FUlzKJpPDHMHOt2aZOVzJtOl4-2526e-253D-26data-3D02-257C01-257Cmark.custer-2540yale.edu-257C55c0eeda5ec04170817308d5f88445be-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C636688169353898109-26sdata-3Dfc-252FunjYJpi8dn2-252BCyS3CiJlzehISoQurnm762VUJ6rc-253D-26reserved-3D0%26d%3DDwMFAg%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Do7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU%26m%3D_W6Y2-L3MuZlIdndB1sqRCYzyVktoECCp37grV7zXr4%26s%3DgJSfQxiaBeCwp9MUsm3MyeKUZjcSTTXwBFJBwXB28U0%26e%3D&data=02%7C01%7Cmark.custer%40yale.edu%7Ca5e4444d211f40520d1308d5f88fef40%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636688219452638990&sdata=nz7E4igwMBv9NG4%2FOP30o%2FOSyi8R%2Bvc78h28M0AC6hk%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__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fdrive.google.com-5Ffile-5Fd-5F1yB8ejKvfSokOMZnWn6k8MjL0CYA6WKkq-5Fview-2D3Fusp-2D3Dsharing-2526d-253DDwMFAg-2526c-253DWO-2DRGvefibhHBZq3fL85hQ-2526r-253Do7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU-2526m-253DylCmqQ0O-2D8R8Z5jgU-5F-2DvjyMALIZcGx3tlGS1iRf0ZZw-2526s-253DgrNFeV-5FE3VHz83XuUpMY3Q84oKgIw4zjEYYB-5FfRTA3I-2526e-253D-26data-3D02-257C01-257Cmark.custer-2540yale.edu-257C55c0eeda5ec04170817308d5f88445be-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C636688169353908109-26sdata-3DwDs5ogJbzTnPVyXrbLX6yv1eznx5cMaUZXlyhVDs6Q0-253D-26reserved-3D0%26d%3DDwMFAg%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Do7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU%26m%3D_W6Y2-L3MuZlIdndB1sqRCYzyVktoECCp37grV7zXr4%26s%3DMCCAIk0pnvdpQChf0oJjySIQx377DaKj-jMRzWe9U_A%26e%3D&data=02%7C01%7Cmark.custer%40yale.edu%7Ca5e4444d211f40520d1308d5f88fef40%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636688219452638990&sdata=tTxav96aI7OoasX9P7fZXKaEwvZF%2FwXFQuDIPpEUAIE%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__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fdrive.google.com-5Fopen-2D3Fid-2D3D1lDMTrXSKp4qzujdCzwhu-2D2DPzomyL0KAlH-2526d-253DDwMFAg-2526c-253DWO-2DRGvefibhHBZq3fL85hQ-2526r-253Do7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU-2526m-253DylCmqQ0O-2D8R8Z5jgU-5F-2DvjyMALIZcGx3tlGS1iRf0ZZw-2526s-253D7eTyX8pwkCAcsXQKjEsqQvxo7Cp4MFnPsQjgqPUgUKQ-2526e-253D-26data-3D02-257C01-257Cmark.custer-2540yale.edu-257C55c0eeda5ec04170817308d5f88445be-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C636688169353918123-26sdata-3D6ytaWPyB9J5-252BC-252F1Vcy6UsZCutjN5WVfKnhlHOeUytlM-253D-26reserved-3D0%26d%3DDwMFAg%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Do7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU%26m%3D_W6Y2-L3MuZlIdndB1sqRCYzyVktoECCp37grV7zXr4%26s%3DI8MiZhuh4mcdNRCzYELZnjgLHbU4qTrx3HbYKUPqo9I%26e%3D&data=02%7C01%7Cmark.custer%40yale.edu%7Ca5e4444d211f40520d1308d5f88fef40%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636688219452648994&sdata=m5ixbhJdQUUMgSrS7az3IoiQVhTO9zzulPDpVxihKbg%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__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fpuitestarchivesspace.library.yale.edu-5F-2526d-253DDwMFAg-2526c-253DWO-2DRGvefibhHBZq3fL85hQ-2526r-253Do7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU-2526m-253DylCmqQ0O-2D8R8Z5jgU-5F-2DvjyMALIZcGx3tlGS1iRf0ZZw-2526s-253DiRqskp189LG1GCTB1pV7exJ3Nb5On6-5F7o1PJaVBmH-2DE-2526e-253D-26data-3D02-257C01-257Cmark.custer-2540yale.edu-257C55c0eeda5ec04170817308d5f88445be-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C636688169353918123-26sdata-3DQgmaLNXt-252Fc9BPspLjJdtdhFgxuy1348xCXyNLrDjihc-253D-26reserved-3D0%26d%3DDwMFAg%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Do7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU%26m%3D_W6Y2-L3MuZlIdndB1sqRCYzyVktoECCp37grV7zXr4%26s%3D7qLoaGqMyglcYOIr-p21jhMRYD08gXz5NUQPuPcSlRs%26e%3D&data=02%7C01%7Cmark.custer%40yale.edu%7Ca5e4444d211f40520d1308d5f88fef40%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636688219452659006&sdata=iGqytc902sZ%2BQDrIDnxE0%2FsOm8UnJ3xh4%2Bk0aFJFrgQ%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 ateve.neiger at yale.edu <mailto:eve.neiger at yale.edu>.
>  
> Best,
>  
> Eve Neiger, on behalf of the Yale University Library ArchivesSpace Public User Interface Implementation Team, Usability and Accessibility Workgroup
>  
> Eve Neiger
> Archivist
> Beinecke Rare Book and Manuscript Library
> Yale University
> 203.432.9027 – eve.neiger at yale.edu <mailto:eve.neiger at yale.edu>
>  
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180802/8ef7efab/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6091 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180802/8ef7efab/attachment.bin>

More information about the Archivesspace_Users_Group mailing list