Certain punctuation creates problems for search in public catalog
Bug #2008423 reported by
Benjamin Kalish
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Triaged
|
Undecided
|
Unassigned |
Bug Description
Currently Evergreen does not handle some subject headings with punctuation well, for example C++ (Computer program language)
A search for subject:C++ (Computer program language) will return works on C and C# as well as C++ resulting in many false positives. On the other hand, a search for subject:"C++ (Computer program language)" returns no results at all.
There should be a way of improving the search experience for folks searching for these headings.
Observed with Evergreen 3-7-3.
Changed in evergreen: | |
assignee: | nobody → Jason Stephenson (jstephenson) |
summary: |
- Punctuation in subject headings creates problems for search + Parenthesis creates problems for search in Angular Staff Catalog |
Changed in evergreen: | |
status: | New → Triaged |
To post a comment you must log in.
I have sort of confirmed this bug and changed the "title" to reflect what I have determined.
First, the "++" is being ignored across the board. I don't remember the exact code or reason why, but it is common in search to ignore symbols. There is likely something that can be adjusted in search indexing or code to change this.
Second, I cannot reproduce the no search results in the OPAC. This only appears to affect the Angular Staff Catalog search.
Third, I cannot reproduce this with a stock 3.10 installation on CWMARS data.
HOWEVER, CWMARS has a security patch installed on production to protect against malicious queries. When that patch is applied to 3.10, I do not get search results in the Angular Staff Catalog for searches containing parentheses. This happens on our produciton 3.7.3 servers and a test server with 3.10 installed looking at a recent copy of produciton data. If I remove that patch on the test server, I get results, so it definitely appears to be that patch.
I am going to update the security bug with a comment to indicate that it appears to be causing this bug.
I have set the status of this bug to triaged pending further review of the security patch.