Nick Clemens 7ca057d03d Bug 26051: We should sort callnumber based on cn-sort ... In zebra we sort by callnumber using 8007 cn-sort We should do the same in elasticsearch To test: 1 - Have Koha using Elasticsearch 2 - Perform a search 3 - Attempt to sort by callnumber 4 - Error in logs: No mapping found for [local-classification__sort] 5 - Apply patch 6 - Restart all 7 - Perform a search and sort by callnumber 8 - Success! Signed-off-by: Fridolin Somers <fridolin.somers@biblibre.com> Signed-off-by: David Nind <david@davidnind.com> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org> (cherry picked from commit a52a0f80b8) Signed-off-by: Fridolin Somers <fridolin.somers@biblibre.com> (cherry picked from commit 726da17134) Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com>		2021-03-05 13:45:05 +00:00
..
Elasticsearch	Bug 26051: We should sort callnumber based on cn-sort	2021-03-05 13:45:05 +00:00
Zebra	Bug 25265: [20.05.x] Prevent double reindex of the same item in batchmod	2020-10-16 14:15:22 +00:00
Elasticsearch.pm	Bug 23828: Elasticsearch - Preserve record order when combining subfield in mappings	2020-11-13 16:12:15 +00:00
Indexer.pm	Bug 25265: [20.05.x] Prevent double reindex of the same item in batchmod	2020-10-16 14:15:22 +00:00
QueryBuilder.pm	Bug 12478: allow more granular sorting configuration	2016-04-26 20:20:08 +00:00
Search.pm	Bug 22721: Remove frameworkcode parameter in GetMarcFromKohaField calls	2019-07-15 11:28:08 +01:00