Thanks, Brian. That JIRA is actually what helped me come up with my theory
earlier in this thread. In our case all of our identifiers have ampersands,
which combined with the exact match issue from the JIRA causes the PUI
identifier search to completely break. Upon digging deeper, it uses
Hi Jesse,
Just FYI, there’s a JIRA for this issue here:
https://archivesspace.atlassian.net/browse/ANW-1556
Brian
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Jesse
Griffis
Date: Thursday, December 15, 2022 at 2:53 PM
To: Archivesspace Users Group
Subject:
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
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:
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
Are you sure the 3.3.1 has finished up indexing 100% of everything? Could be
it's stuck. Check the logs for ERROR or FATAL
It may also be the search just returns things a bit differently in 3 vs 2, but
I'd make sure there's not an indexing issue first.
Can you get the record to show up in
Good Afternoon All,
My team is in the process of upgrading from 2.8.0 to 3.3.1 and we're
encountering an odd error. In our 2.8.0 version we are able to search by
identifier and obtain a specific record in the PUI. The same search in 3.3.1
returns no records. We would greatly appreciate any
