https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30836
--- Comment #6 from David Cook <dc...@prosentient.com.au> --- (In reply to Ere Maijala from comment #5) > I'm not sure if I can come up with a good solution. Automatically updating > current mappings can create problems when the defaults have been customized. This reminds me that we have this problem in other parts of Koha as well, and we've never found a good solution. For example, MARC Bibliographic Frameworks. Also, "Koha to MARC mapping". (In reply to Ere Maijala from comment #5) > What we might be able to do is to check, field by field, if the mappings > have been customized, and apply any changes only on top of old defaults. I'm > not sure if that's feasible in real life, but worth a thought. At least it > should be possible to check that any mappings required by Koha are available > regardless of their configuration, and add any that are missing completely. > Perhaps a warning about updated mappings during upgrade would be useful as > well. Actually... I think that this is probably the way to go. I'm not familiar with the Elasticsearch mappings setup, but in theory couldn't you compare default values against user-generated values? And then update everything but those? And then maybe have some way of telling users which values are default and which values aren't in a visual way? I imagine that might be easier for Elasticsearch mappings than it would for say "MARC Bibliographic Frameworks". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/