emory-libraries / blacklight-catalog

1 stars 2 forks source link

spike - investigate possible bug with unintended limiters #1407

Closed tclayton33 closed 6 months ago

tclayton33 commented 7 months ago

Multiple users at the Theology library are reporting issues with Advanced search applying limiters that they did not choose. It seems to be an intermittent but recurring issue that is happening across different browsers, including incognito sessions.

Several (but not all) examples involved the "language=latin" and a "title starts with" limiter being applied. Example - user searches for title=Marriage AND Authur=Reynolds, but search also applies Language=Latin AND Title starts w/ L.

Advanced search and uninteded limiters1.png

Or the user is performing and advanced search for a local call number, such as "1511 GEIL" but the search adds a limiter for subject display ssim = Bible-periodicals-indexes.

advanced search unintended limiters2.png

Users have been advised to clear previous searches by using the "start over" button. Bo states that "The “start over” option does not fix the problem. Manually removing each superfluous limiter by clicking the “x” next to it is the only way to get the results one wants

Other observations from Bo:

unintended limiters.png

So far, I have not been able to replicate this issue. We need to determine if this is a bug, user error, or something that needs an enhancement request.

I've created a document in the Library Search Committee's Sharepoint that we can use to collect more examples and information directly from library staff who are experiencing this issue.

abelemlih commented 7 months ago

This issue is likely due to irrelevant search data persisting between searches due to the caching we implemented in this ticket. I deployed branch abel-1407-fix_advanced_search to Test to verify that disabling caching resolves all the issues currently seen in production. Disabling caching will lead to the same performance issues we have seen previously, so we will need to develop a new solution for that issue.

tclayton33 commented 6 months ago

this was resolved w/ #1411