Bug 41669

Summary: Elasticsearch mappings should show if user edited or default from mappings.yaml
Product: Koha Reporter: David Cook <dcook>
Component: Searching - ElasticsearchAssignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: e.betemps
Version: Main   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23204
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22639
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:

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.)