| Summary: | Relevance does not work properly when using QueryParser | ||
|---|---|---|---|
| Product: | Koha | Reporter: | David Cook <dcook> |
| Component: | Searching | Assignee: | Galen Charlton <gmcharlt> |
| Status: | CLOSED WONTFIX | QA Contact: | Testopia <testopia> |
| Severity: | major | ||
| Priority: | P5 - low | CC: | eric.vantillard |
| 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: | |||
| Bug Depends on: | |||
| Bug Blocks: | 12742 | ||
|
Description
David Cook
2014-06-17 07:28:05 UTC
Try doing a "Title" search or a "Subject" search and you'll see that results are returned in ascending biblionumber order and not in order of relevance. The following references should probably be either removed or have 2: 102 commented out.
This adds relevance to the entire query, which is probably not what we want to do, since adding relevance to a query containing date indexes/sub-queries causes unexpected results or no results for that date sub-query.
If we do a callnumber search, we might also get distorted results where records with lots of items with that callnumber undesirably rise to the top.
relevance:
bib1_mapping:
biblioserver:
2: 102
enabled: 1
label: Relevance
relevance_dsc:
bib1_mapping:
biblioserver:
2: 102
enabled: 1
label: Relevance_dsc
relevance_asc:
bib1_mapping:
biblioserver:
2: 102
We've voted to remove the QueryParser code (https://wiki.koha-community.org/wiki/Development_IRC_meeting_4_March_2020), so I am closing this WONTFIX. |