[Archivesspace_Users_Group] ASpace search glitch (staff interface)

[Blake Carver]

Hi Ron,
Did the reindex finish and it's still throwing that error?
Any errors while indexing?
-Blake


________________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Stanonik, Ronald <rstanonik at ucsd.edu>
Sent: Friday, October 13, 2017 2:04:33 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch   (staff  interface)

I did a little testing and it appears that double quotes fail, but single quotes succeed.
Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald
Sent: Friday, October 13, 2017 9:46 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hi,

I’m a system administrator for UCSD Library and I’m attaching a stacktrace from the error that Laurel reported.

I’m forcing a solr reindex (removed Indexer_state) to see if that helps.

Any other suggestion appreciated.

Thanks,

Ron

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] On Behalf Of McPhee, Laurel
Sent: Friday, October 13, 2017 7:54 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Cc: Christensen, Marlayna <mkchristensen at ucsd.edu<mailto:mkchristensen at ucsd.edu>>
Subject: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hello,

I have a puzzling search problem that I can’t recreate in the sandbox. We recently upgraded to v2.1.2. General keyword searching works find in the staff interface, but if we enclose any search terms in quotes, for example, “Theatre and Arts Foundation” we get the lovely white screen/bold red text message: We’re sorry, but something went wrong, even though we have a collection named Theatre and Arts Foundation Records.  We’ve tried this with lots of different word combinations that we know should work fine and retrieve results—same error message.

However, if I search for the resource or accession number for any collection in quotes, such as “mss 0152”, the correct collection pops right up, so the use of quotes is not a total deal-breaker in our search. I was thinking I’d go to the sandbox and smugly recreate the problem and report it, but using some of the sample collections in there to do quotes-enclosed searches, everything worked perfectly. What could be going wrong at UCSD? Thank you for any insight!

Laurel