https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38006
--- Comment #5 from Phil Ringnalda <[email protected]> --- Sorry. Being a ByWater partner in a consortium where catalogers range from full-time advanced editor users to elementary school library aides whose training is handed down third-hand at best, you would think I would have recognized the data loss potential. It's filed as an enhancement, which is a bit low for a data loss bug, which ought to at least be major. And I still don't see what thing it's actually aiming to fix, only one possible fix presented not as a fix for a particular problem, but as something which must be done because it's self-evident that doing it is the right thing to do. Is it "the Fast Add framework is alphabetically right next to one we use all the time, and if we accidentally pick the wrong one then when someone opens it in the basic editor and saves, everything but the Fast Add fields are gone"? Or is it "when our advanced editor users need to upgrade a Fast Add record, even though it opens in the basic editor they will switch over to the advanced editor, and then if they forget to switch the framework away from Fast Add, a later edit in the basic editor will wipe out their upgrade"? Both of those could be fixed by just not showing the Fast Add framework in the framework chooser (and either refusing to open an FA record, or automatically switching frameworks, if someone tries to open an existing one), since Koha goes to great lengths already to avoid having you ever edit one there. Or is it something other than one of those? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ 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/
