Bug 22340 - Elasticsearch - sorting fields should have a fallback mechanism
Summary: Elasticsearch - sorting fields should have a fallback mechanism
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching - Elasticsearch (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-14 15:41 UTC by Nick Clemens (kidclamp)
Modified: 2024-02-19 16:08 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Clemens (kidclamp) 2019-02-14 15:41:35 UTC
As an example

264 and 260 should be sortable for publisher

Some records will have one, some will have both, it should eb configurable which to use and that we should not leave the sort field empty if one field is missing
Comment 1 Andreas Jonsson 2024-02-19 16:08:50 UTC
In the field mappings of the search engine configuration there could be an integer option "sort fallback order".  So, when indexing, the sort field is filled with the values corresponding to the mappings with "sort fallback order" = n for the smallest n where the corresponding fields are nonempty.