Currently, when using QueryParser, relevance will only work for keyword queries. queryparser.yaml either needs to be updated to include more weighted relevance mappings, or QueryParser needs a mechanism to add relevance to queries beyond the limited support it currently has. More information available here: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12430
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.