From 54937c5eb34c511e00de8d0831141516422885c7 Mon Sep 17 00:00:00 2001 From: Jonathan Druart Date: Fri, 15 Nov 2013 11:10:04 +0100 Subject: [PATCH] Bug 11255: allow "relevance ascending" as a sort option This patch fixes a problem where if a staff member sets the *defaultSortField/*defaultSortOrder system preferences to relevance ascending while QueryParser is enabled, default keyword search would break -- the query parser config did not declare relevance asc as a possible "modifier". Note that setting the sort order to relevance ascending does not actually make catalog search return results with the least relevant records showing up first; Zebra does not support such a mode. In other words, relevance ascending acts exactly the same as relevance descending. Test plan: 0/ Create some biblio with "history" in the title and ensure that the QueryParser system preference is enabled. 1/ Define prefs defaultSortField = relevance and defaultSortOrder = asc 2/ Search "history" on the staff interface 3/ Note that no result is returned. 4/ Apply the patch 5/ Verify the queryparser config file in use takes the modification into account (see the queryparser_config value in your $KOHA_CONF file). 6/ Relaunch the search and verify results are returned Signed-off-by: Christopher Brannon Signed-off-by: Kyle M Hall Signed-off-by: Galen Charlton --- etc/searchengine/queryparser.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/etc/searchengine/queryparser.yaml b/etc/searchengine/queryparser.yaml index 0cce85cc07..53cff85f04 100644 --- a/etc/searchengine/queryparser.yaml +++ b/etc/searchengine/queryparser.yaml @@ -1427,6 +1427,12 @@ modifier_mappings: 2: 102 enabled: 1 label: Relevance_dsc + relevance_asc: + bib1_mapping: + biblioserver: + 2: 102 + enabled: 1 + label: Relevance_asc title-sort-az: bib1_mapping: biblioserver: -- 2.39.5