Bug 24006 - Switching on QueryWeightFields (relevance ranking) breaks search
Summary: Switching on QueryWeightFields (relevance ranking) breaks search
Status: RESOLVED DUPLICATE of bug 12430
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching - Zebra (show other bugs)
Version: 18.11
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-11 11:26 UTC by Bernard
Modified: 2020-12-03 05:53 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernard 2019-11-11 11:26:11 UTC
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.
Comment 1 Katrin Fischer 2019-11-13 22:40:28 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.
Comment 2 Fridolin Somers 2020-06-30 11:42:38 UTC
(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.
Comment 3 David Cook 2020-12-03 05:53:49 UTC
I think that this is a duplicate of Bug 12430

*** This bug has been marked as a duplicate of bug 12430 ***