[Bug 41669] New: Elasticsearch mappings should have user_edited flag
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41669 Bug ID: 41669 Summary: Elasticsearch mappings should have user_edited flag Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs@lists.koha-community.org Reporter: dcook@prosentient.com.au QA Contact: testopia@bugs.koha-community.org 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.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41669 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=23204 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41669 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=22639 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41669 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Elasticsearch mappings |Elasticsearch mappings |should have user_edited |should show if user edited |flag |or default from | |mappings.yaml -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41669 Emmanuel Bétemps <e.betemps@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |e.betemps@gmail.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41669 Thomas Klausner <domm@plix.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |domm@plix.at --- Comment #1 from Thomas Klausner <domm@plix.at> --- 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. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41669 --- Comment #2 from David Cook <dcook@prosentient.com.au> --- (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.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org