http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5572
--- Comment #22 from Janusz Kaczmarek <janus...@gmail.com> --- (In reply to comment #20) > I do not think this is correct. Subfield 'e' is not authority-controlled, > but Koha treats all non-numeric subfields in authority-controlled fields as > if they are. Or am I misunderstanding what this bug does, and there is a > workaround for this? OK, the action of the modified merge procedure is based on "Select to display or not" (i.e. auth_subfield_structure.hidden) and of course one has to be cautious about it. If a subfield of the heading is hidden in authority editor == it not supposed to be controlled == will never be overwriten. This would be the case of auth. 100 applied on biblio. 700 with $e present. $e will stay untouched provided it is not active in the authorities framework. Why I now think it is really important: a very common case for my libraries (participating in a cooperative cataloguing program) are personal headings with duplicated family name + surname. So, if the librarian who creates the entry does no know the dates, he/she adds a qualifier like $c. But then another librarian who found the dates (maybe after some months or even years) exchanges $c for $d in the authority data. Now, without this enhancement you will have $c and $d in bibliographic records, which is what you don't want. Another reason is the case when wrongly entered data was propagated to several dozens of biblio recs. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org 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/
