http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5572 Jared Camins-Esakov <jcamins@cpbibliography.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jcamins@cpbibliography.com --- Comment #20 from Jared Camins-Esakov <jcamins@cpbibliography.com> --- (In reply to comment #2)
(In reply to comment #1)
Tested your patch: it works as described. I see your point when you should clear a subfield at the authority side and you want to see the same at the biblio side. [How often would that happen?]
Well, me myself was not convinced that it happens and that such a refinement is is necessary--it was the library staff that told me it really happens sometimes and demanded to make Koha to behave like described in the proposal. It does not happen often perhaps, but if it happens then the staff would have to edit even hundreds of biblio records by hand without this refinement.
However, if the subfield was already empty at the authority side and you update the auth record, do you also want to clear at that moment any possible info in that subfield at the biblio side?
Yes, because I was told this exactly means that the set of subfields of a field in biblio is *controlled* by the authority record. In other words, if a subfield can have a value in authority (in Koha: it is not in 'ignored' state), then you are not supposed to edit it by hand in biblio. I do not know if it is really so--I was told that.
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?
Does an empty authority subfield that is "not in the ignore tab" in the framework, really mean that that subfield should always be empty too at the biblio side? I am not sure about that; I will copy this comment to the Koha list for possible further discussion.
At least this is what I was told. This means of course that with my refinement you have to carefully check which subfields are active in the authority framework, in order not to delete what you do not intend to.
I will appreciate any comments. For now this is what was needed in my library. I thought it worth to share this with others.
-- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.