Bug ID: 19575
Summary: Use canonical field names and resolve aliased fields
Change sponsored?: ---
Priority: P5 - low
Component: Searching - Elasticsearch
Assignee: [hidden email] Reporter: [hidden email]
The current elastic search fields seems to be a mix between zebra aliases,
field names, some duplicates and new fields. This causes issues with sorting in
UI and hard-coded search-links in XSL-templates for example. I have attempted
to clean things up a bit, which resolves many of these issues. I might not have
the time to do so today, but will attempt to find and mark all current issues
resolved by this fix.
--- Comment #3 from David Gustafsson <[hidden email]> ---
Think I have missed a few places (facets for example) where field names are
hard coded and needs to be changes. So no point in trying out patch in it's
current state until these things are fixed.
--- Comment #7 from David Gustafsson <[hidden email]> ---
Think I have been looking at the Zebra-mapping configuration in the wrong place
(this old config, not biblio-koha-indexdefs.xml). I will go through the mapping
changes one more time using this as reference instead.
--- Comment #10 from David Gustafsson <[hidden email]> ---
Wrote a script to extract mappings from biblio-koha-indexdefs.xml and convert
to mappings.yaml, left the fields with existing mapping-targets as they are
(even though discovered several discrepancies with the Zebra mappings) and
mostly just added the missing fields. Will now do more thorough local testing
so will probably adjust this patch some more before ready to be reviewed.