| Summary: | "sn:" shortcut to search by biblionumber is too broad | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Andrew Fuerste-Henry <andrew> |
| Component: | Searching - Elasticsearch | Assignee: | Bugs List <koha-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 - low | ||
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
If I change SearchEngine back to Zebra, with QueryAutoTruncate set to "automatically," it somehow knows not to truncate this search. Hm, so the problem is that it should not truncate with Zebra? In what context are we using sn for searching biblionumbers instead of biblionumber? |
Searching for "sn:1" seems to be returning every bib with a 1 in its bib number. "sn:100" only returns bib 100. Turned on DumpSearchQueryTemplate and pulled this from the source when searching "sn:1": 'query' => '(local-number:1*)', 'default_operator' => 'AND', 'lenient' => $VAR1->{'search_query'}{'query'}{'query_string'}{'analyze_wildcard'} } },