Searching the catalog for a phrase match fails when the search term begins or ends with certain characters.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Undecided
|
Unassigned | ||
2.10 |
Fix Released
|
Undecided
|
Unassigned | ||
2.8 |
Fix Released
|
Undecided
|
Unassigned | ||
2.9 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Evergreen 2.5.1 + (?)
Does not appear to be a problem in a 2.3.5 system, at least not in the one 2.3.5 system I was able to identify (catalog.
When searching the catalog for terms in quotes, implying that an exact phrase match is desired, if the term begins or ends with punctuation and other non-alphanumeric characters, no hits are found.
Example searches are:
"o, africa!"
"o.o.p.s."
"$30 music school"
"$60 a day"
"footballers wive$"
"westward ho!"
"are you being served?"
"61*"
Eliminating the beginning or ending character within the quotes, and searching these terms without quotes does yield results. This happens in both title and keyword indices.
This is true in all Evergreen catalogs tried so far on releases 2.5 and up. For the "o, africa!" search, below are links to several catalogs. The first link is the search with the quotes, the second without the quotes. Note that the last set of links is the 2.3.5 system, and the quoted search is successful:
NOBLE (2.6.2):
http://
MVLC (head):
http://
http://
CWMARS (2.5.5):
http://
Bibliomation (head):
http://
Pines (2.5.1):
https:/
https:/
TADL (2.5.1):
http://
http://
NTLC (2.3.5)
http://
Changed in evergreen: | |
milestone: | none → 2.next |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Changed in evergreen: | |
milestone: | 2.next → 2.11-alpha |
Also noting that while a search for "o, africa!" fails, a search for "o, africa! : a novel" is successful, so it definitely seems to only be having trouble with punctuation at the beginning or end.
I think there are times when we want the ending punctuation to be ignored, especially when it is punctuation like a / that is not part of the title, but is part of cataloging practice. However, when the punctuation is part of the title, it should work.
Given the results of the 2.3 testing, I'm wondering if this change occurred as part of the large query parser changes that came with 2.4?
Michele, I removed the word exact from the title of the bug report so that it doesn't get confused with the "Matches Exactly" search option, which works a bit differently.