| Summary: | Hyphen in branchcode gives wrong search results | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Caroline Cyr La Rose <caroline.cyr-la-rose> |
| Component: | Searching | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | clemens.tubach, dcook, katrin.fischer, michaela.sieber |
| Version: | Main | Keywords: | Manual |
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Caroline Cyr La Rose | Documentation submission: | https://gitlab.com/koha-community/koha-manual/-/merge_requests/626 https://gitlab.com/koha-community/koha-manual/-/merge_requests/627 |
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Caroline Cyr La Rose
2021-05-31 20:43:10 UTC
Hi Caroline, that's a known issue. The search by library and others are keyword searches. hyphens are treated as spaces, so FFL-N is "FFL S" and a search for FFL will find it. Same is true for locations, collections etc. I don't think changing the hyphen behavior in general would be a good idea as we want that for normal search. Using "ext" (exact field search) was problematic in the past - it didn't work for libraries using ICU. Not sure if it does now. Safest option might be to avoid hyphens in the codes. To add in the manual, no hyphens in branchodes, loc, CCODE Not really fixed, but I added the info in the manual... hopefully bug 28495 will prevent users from making mistakes Is this still valid? I can not recreate this (with Elastic) We have more than 150 branchcodes with hyphens but never had problems since we started to migrate to Koha (I think we started with Version 21.11) Or is this only a problem with Zebra? I would imagine it's a problem with Elastic too, but depending on your search terms. The problem arises here: branchcodes: A A-B So when searching for A you'd also find A-B, because they are treated as words. (In reply to Katrin Fischer from comment #5) > I would imagine it's a problem with Elastic too, but depending on your > search terms. The problem arises here: > > branchcodes: > A > A-B > > So when searching for A you'd also find A-B, because they are treated as > words. Yeah I'd say it's probably a problem. The same problem exists throughout Koha. Item types, collection codes, locations, etc. |