https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38006
Donna <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Donna <[email protected]> --- I would think, that for anyone who does cataloging, that ANY unwarned data loss is a huge deal. I think this is more noticed by ByWater team because we work with a lot of libraries that have multiple levels of catalogers, and work is done in both advanced and basic editors, and often by different people, so we pay particular attention when a partner points out that they are losing data. This has nothing to do with editing the default framework and how you should do it. It is about being able to add non-retained fields when working in a framework in the advanced editor. There absolutely should be a warning that the field being added is not part of the framework and the data will be lost. I'm not sure why a bug aimed at preventing data loss is the cause for such a strong and negative reaction - what would be the issue with correcting this? -- 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/
