https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41669
--- Comment #2 from David Cook <[email protected]> --- (In reply to Thomas Klausner from comment #1) > I guess an easy and correct workflow could be to download / export the > current mappings into a file and diff this file with the new mappings. Then > you could resolve the conflicts in the yaml file and upload / import it when > you're done. > > It'a a bit more cumbersome, because you have to "leave" Koha for that, and > it requires some semi-advanced skill (using diff), but if we document this > it could be much less work than adding what you suggested to our code. I will be glad when bug 22639 is pushed as I think being able to export current mappings will be very valuable for sure. But you'd have to remember to do the export before doing the upgrade. And it wouldn't necessarily be clear what needs to be preserved when doing a diff either. I wonder if we should have some automated exports/backups of Elasticsearch settings. Certainly at upgrade time. Maybe even at edit time? At the moment, it's very easy to lose custom mappings that are entered through the web UI :/ -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] 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/
