Summary: | Make it possible to ignore apostrophe in searching (Zebra) | ||
---|---|---|---|
Product: | Koha | Reporter: | Aleisha Amohia <aleisha> |
Component: | Searching - Zebra | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | dcook, hacheng |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27153 | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Aleisha Amohia
2025-04-10 05:34:37 UTC
I wonder how that could work with the Zebra configuration files as we cannot change them on the fly and manipulating the search query doesn't seem to be enough as I think you'd always have to change how things are indexed (ignoring apostrophes or not). I believe by default the normal apostrophes are ignored or could be added to the instance specific index configuration files (there is option option to have them instance specific IIRC, but we haven't used that feature) From memory, Koha's Zebra config currently turns "David's" into "David s" using the ICU rules. I don't know allt he details of bug 27153, but we probably could use the XSLTs to add a z:index entry for title-no-punctuation that would be "Davids" and have title be "David's", and then the ICU rule will just affect "title" and not "title-no-punctuation". I haven't looked at bug 27153 in a while though, so I'd have to review it to know what we're doing there for sure. And actually... since the Zebra XSLTs are generated from the XML... it might be quite annoying to achieve this anyway... |