[Bug 38741] New: define a secondary sort order search results where primary sort field matches for several results
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38741 Bug ID: 38741 Summary: define a secondary sort order search results where primary sort field matches for several results Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs@lists.koha-community.org Reporter: jake.bateman@ptfs-europe.com QA Contact: testopia@bugs.koha-community.org When several search results are returned whose relevance and defaultSortOrder field match (a series with many volumes with the same publication date, in my case), it would be desirable to have these results ordered by some deliberately chosen field, or by a sensible default (title alphanumeric desc would I think would be correct in all cases, potentially negating the need for an additional syspref). In my testing (with Elasticsearch), I believe the current secondary sort order to be [biblionumber asc, plus some randomness from a race condition introduced by the multiple concurrent processing threads used by the Elasticsearch reindex task, if multithreading was used]. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38741 Jake Bateman <jake.bateman@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|define a secondary sort |define a secondary sort |order search results where |order for searches where |primary sort field matches |primary sort field matches |for several results |for several results -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38741 --- Comment #1 from Jake Bateman <jake.bateman@ptfs-europe.com> --- screenshots of an example search with records in semi-random but almost biblionumber order https://imgbox.com/muwIxR4O https://imgbox.com/TO0X2pYG -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38741 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=23875 --- Comment #2 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I thought we had fixed the biblionumber not sorting numerical... but maybe not? I remember the intention to use it as the second sort criteria and I think we would like that as an option at least. It would allow to put the newest (highest biblionumber) first. Which version are you testing with? There is also: Bug 23875 - Elasticsearch - When sorting by score we should provide a tiebreaker -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38741 helm.consortium@nhs.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |helm.consortium@nhs.net -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org