Bug 18827 - Elasticsearch mappings - not displayed or retrieved in saved order
Summary: Elasticsearch mappings - not displayed or retrieved in saved order
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching - Elasticsearch (show other bugs)
Version: master
Hardware: All All
: P5 - low normal (vote)
Assignee: Nick Clemens
QA Contact:
URL:
Keywords:
: 19922 (view as bug list)
Depends on: 14899
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-19 20:12 UTC by Nick Clemens
Modified: 2019-02-20 20:18 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Who signed the patch off:
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 2017-06-19 20:12:52 UTC
The mappings listed under 'Biblios' and 'Authorities' are draggable - this allows ordering of fields.

The ordering affects the id field in the search_marc_map table

When retrieving for display or mapping we are not ordering by the this field.


In general I am not sure if we are gaining anything with this ordering:

https://www.elastic.co/guide/en/elasticsearch/guide/current/_sorting.html
" When sorting on fields with more than one value, remember that the values do not have any intrinsic order; a multivalue field is just a bag of values. Which one do you choose to sort on?"

I think we can switch to the idea that a single field per index should be chosen for ordering:
author = 100 (only make this one sortable)
author = 700
author = 245c


or, in the case of authorities, we should expect a single field to populate the field for sorting (100, 110, 150 ... are alldefined as 'main-heading' - but each record should only have a single one of these field)
Comment 1 Joonas Kylmälä 2018-10-09 11:45:09 UTC
*** Bug 19922 has been marked as a duplicate of this bug. ***