[Archivesspace_Users_Group] Issue with searching by identifier in PUI

[Brian Harrington]

Hi Jesse,

Just FYI, there’s a JIRA for this issue here:  https://archivesspace.atlassian.net/browse/ANW-1556

Brian

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jesse Griffis <jagriffis at mail.wvu.edu>
Date: Thursday, December 15, 2022 at 2:53 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in PUI
Thanks for the idea. From a quick test it appears that searching by identifier requires an exact match and doesn't work with wildcards in 3.3.1. Strangely partial matches and wildcards do work in 2.8.0.

Jesse Griffis
Prof. Tech. 2
Systems Development
WVU Libraries
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Thursday, December 15, 2022 2:33 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in PUI

A potential test/workaround would be to replace the ampersand with a wildcard '*' in your searches. If that wildcard search works, I think it would confirm your idea about the ampersand translation.

jds
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jesse Griffis <jagriffis at mail.wvu.edu>
Sent: Thursday, December 15, 2022 2:23 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in PUI

You don't often get email from jagriffis at mail.wvu.edu. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>

Thank you for the advice. I believe we waited for the index to finish completely, but I will double check that. We are able to find the record through regular keyword searches, and in the staff UI we can find it using the exact same identifier search term. I have a theory that it may have something to do with input sanitization on the PUI side as well as the issue with identifier truncation mentioned in https://archivesspace.atlassian.net/browse/ANW-1556<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fbrowse%2FANW-1556&data=05%7C01%7Cjoshua.d.shaw%40dartmouth.edu%7C285e48f5beaa440cd58408daded1e1ac%7C995b093648d640e5a31ebf689ec9446f%7C0%7C0%7C638067290885360987%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bOlRnYdKFFIjFL8tGmvHyzfOLB6A1QB7gnKOhZiLEJk%3D&reserved=0> . The identifier in question has an ampersand which gets translated to "&" in the PUI search and since that isn't an exact match to the identifier it doesn't get returned. I've been trying to figure out a way to fix the ampersand issue and test this theory.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221216/60a4ac9a/attachment.html>