| Summary: | Switching on QueryWeightFields (relevance ranking) breaks search | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Bernard <bernard.scaife> |
| Component: | Searching - Zebra | Assignee: | Bugs List <koha-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 - low | CC: | dcook, fridolin.somers |
| Version: | 18.11 | ||
| 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: | |||
|
Description
Bernard
2019-11-11 11:26:11 UTC
It should do some kind of relevance ranking without. Debugging search issues is hard, but what I would recommend is doing your testing again with and without QueryAutoTruncate - there is a known bug of it breaking relevance. (In reply to Bernard from comment #0) > eg/ using simple search in OPAC > > QueryWeightFields (enabled) > > flute AND oboe = 701 > flute OR oboe = 115 > flute NOT oboe = 10 > > QueryWeightFields (disabled) > > flute AND oboe = 1038 > flute OR oboe = 3983 > flute NOT oboe = 2121 > > The results from the "disabled" look correct but of course there is no > longer any relevance ranking. With QueryWeightFields on, boolean are considered like string, on purpose. The search terms are around quotes. |