Bug 18294 - Keyword searches surrounded by double quotes fail on staff client and OPAC
Summary: Keyword searches surrounded by double quotes fail on staff client and OPAC
Status: RESOLVED DUPLICATE of bug 16863
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching - Zebra (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Galen Charlton
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-17 12:58 UTC by Barton Chittenden
Modified: 2023-09-10 16:12 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Barton Chittenden 2017-03-17 12:58:03 UTC 
To replicate:

A keyword search for

    juggling for the complete klutz

    or a single quoted version of the same:

    'juggling for the complete klutz'

on https://demo.bywatersolutions.com returns the following result: https://demo.bywatersolutions.com/cgi-bin/koha/opac-detail.pl?biblionumber=36263


The same search, surrounded by double quotes returns no hits:

    "juggling for the complete klutz"

https://demo.bywatersolutions.com/cgi-bin/koha/opac-search.pl?q=%22juggling+for+the+complete+klutz%22&branch_group_limit=

... RESULTS OF SEARCH FOR 'KW,WRDL: "JUGGLING FOR THE COMPLETE KLUTZ"'
No results found!
No results found for that in ByWater Library System catalog. 

Sorry we didn't find what you were looking for

[Replicated under 16.11.04.001]
Comment 1 Barton Chittenden 2017-03-17 13:58:04 UTC 
Note that this issue is separate from the URL encoding issues in Bug 13301.
Comment 2 Tomás Cohen Arazi (tcohen) 2017-05-09 19:31:20 UTC 
(In reply to Barton Chittenden from comment #1)
> Note that this issue is separate from the URL encoding issues in Bug 13301.

Barton, have you tried enabling the QueryParser? I'm more inclined to fix the QueryParser if there are issues with it, and stop spending time on the legacy query parsing code.
Comment 3 Magnus Enger 2017-05-09 19:33:31 UTC 
I had a customer complaining about this exact issue. Setting UseQueryParser = Try solves it.
Comment 4 Magnus Enger 2017-05-09 19:35:35 UTC 
(In reply to Magnus Enger from comment #3)
> I had a customer complaining about this exact issue. Setting UseQueryParser
> = Try solves it.

Not sure if that might cause other issues, though...
Comment 5 Katrin Fischer 2020-04-19 11:10:43 UTC 
This bug is a bit strange and still valid. 

I can not replicate it on my test instance with master and Zebra or on our 18.11 installation.

But it still appears broken on Bywater's installation as linked here. I wonder if it's anything to do with configuration and where to start looking.

Switching the QueryParser on is NOT a solution, as we just removed the QueryParser from the code.
Comment 6 Katrin Fischer 2023-09-10 16:12:03 UTC 

*** This bug has been marked as a duplicate of bug 16863 ***