https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41051 Bug ID: 41051 Summary: QueryFuzzy syspref description not clear about how it affects Elasticsearch. Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs@lists.koha-community.org Reporter: alex@rcls.org QA Contact: testopia@bugs.koha-community.org CC: aude.charillon@openfifth.co.uk, david@davidnind.com, philip.orr@lmscloud.de An otherwise intelligent sysadmin may wonder why Elasticsearch fuzzy searches with "~" don't work and go looking for answers. The current phrasing of the QueryFuzzy syspref is unclear and suggests that the syspref only affects users of Zebra. This is not the case, as the syspref must be set to "Try" on Elasticsearch systems as well in order to enable fuzzy searches. Current phrasing: [Try/Don't Try] to match similarly spelled words in a search. (For example, a search for flang would also match flange and fang; Currently only affects Zebra searches. Any Elasticsearch term can be made fuzzy by adding a ~ directly after the term.) Suggested wording: [Try/Don't Try] to match similarly spelled words in a search. (For example, a search for flang would also match flange and fang.) If using Zebra, searches become fuzzy by default. If using Elasticsearch, a term must be made fuzzy by adding a ~ directly after the term. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.