Summary: | define a secondary sort order for searches where primary sort field matches for several results | ||
---|---|---|---|
Product: | Koha | Reporter: | Jake Bateman <jake.bateman> |
Component: | Searching - Elasticsearch | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | helm.consortium |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23875 | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Jake Bateman
2024-12-18 12:21:00 UTC
screenshots of an example search with records in semi-random but almost biblionumber order https://imgbox.com/muwIxR4O https://imgbox.com/TO0X2pYG 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 |