Bug 41669 - Elasticsearch mappings should show if user edited or default from mappings.yaml
Summary: Elasticsearch mappings should show if user edited or default from mappings.yaml
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching - Elasticsearch (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-21 01:14 UTC by David Cook
Modified: 2026-01-21 08:02 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:14:03 UTC
Out of the box, Elasticsearch's mappings in the database are populated by the mappings.yaml. It's alwasy possible to re-populate the database by "resetting" the configuration.

You often need to do this after an upgrade to get all the new defaults. But if you do that, you lose all your customizations.

It would be nice to have a "user_edited" to denote mappings that have been added/edited by users via the web UI. Having a visual cue that these are custom fields would be great.

(If we had an option to retain those fields during a reset, that would be even more amazing. Although that's more complicated.)