Bug 41670 - Elasticsearch mappings.yaml does not match mappings export out of the box
Summary: Elasticsearch mappings.yaml does not match mappings export out of the box
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching - Elasticsearch (show other bugs)
Version: Main
Hardware: All All
: P5 - low minor
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 23204
Blocks:
  Show dependency treegraph
 
Reported: 2026-01-21 01:41 UTC by David Cook
Modified: 2026-01-21 08:03 UTC (History)
1 user (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Cook 2026-01-21 01:41:29 UTC
If you run export_elasticsearch_mappings.pl using a default mappings configuration, you'll export a file which differs from usr/share/koha/intranet/cgi-bin/admin/searchengine/elasticsearch/mappings.yaml

One difference is that the export contains the "filter" field whereas the default mappings.yaml does not.

Another difference is that the "unimarc" fields aren't included in the output, although that makes a certain sense... (although it makes it tougher to do diffs)

Other-control-number for authorities isn't included in the export. (I'm guessing because of a clash with other-control-number from biblios because in the DB it's lowercased as other-control-number...)

Current-publication-frequency appears in a different place...

title-no-punctuation appears in a different place...

The mandatory field for "title" is different is 1 in mappings.yaml but ~ in the export.
Comment 1 David Cook 2026-01-21 01:44:58 UTC
In the export, some fields have authorised_value_category whereas mappings.yaml doesn't