http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12477
Jacek Ablewicz <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #9 from Jacek Ablewicz <[email protected]> --- (In reply to David Cook from comment #8) > If a field doesn't appear in the Editor, and it gets re-saved...any fields > not appearing in the Editor will be destroyed. Does it really work that way for biblos MARC frameworks?? If so, that would be a _major_ disaster IMO. I was under the impression that if the certain subfields are set up as "hidden in editor", they still get saved (not getting destroyed on re-save). Also, at least in the manner of speaking, they do appear in editor ;), their contents are just not visible and not editable (AFAIRC authority editor uses "display: none" for that purpose, I'm not sure about biblio editor). > I figure...if it doesn't appear in the Editor, it probably _doesn't_ need to > appear anywhere else. There are some scenarios when we e.g. may want some fields/subfields to be: preserved in the MARC record (control numbers, some linking data for records imported from union catalogues etc.), visible in staff client, but not directly editable by the librarians. Possibility to define (perhaps even greatly) simplified frameworks, intended for some specific editing tasks (= with a lot of existing record fields/subfields hidden on edit) might often come in handy as well. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
