https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38213 Bug ID: 38213 Summary: Fix problems with MARC21 003 being mandatory Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs@lists.koha-community.org Reporter: phil@chetcolibrary.org QA Contact: testopia@bugs.koha-community.org CC: katrin.fischer@bsz-bw.de, m.de.rooy@rijksmuseum.nl In the MARC21 frameworks we ship, 003 is mandatory in Default and thus in the optional frameworks like BKS since they copy mandatory from Default. However, the optional frameworks set 003 to hidden = -6, which is visible in the OPAC and staff interface but not in the (basic) editor. That means that if you create two records in BKS in the basic editor, you cannot set a value for 003, and then if you try to merge them you will not be able to merge, because 003 is mandatory but not present in either record and merging records enforces mandatories. We could fix that for future installations by not setting hidden to -6 in the optional frameworks, so that they would require setting 003 just like Default does. Or, we could fix it by not setting 003 mandatory. 003 is the marcorg code for the organization whose control number is in 001, but we don't set 001 as mandatory so we require a code for the organization which set the control number '' so that '(code)' will be a globally-unique control number, which is nonsense. It also creates nonsense when you import a naughty record which has a 001 but no 003, since then you will click in the 003 and have marc21_orgcode.pl fill in your marcorg code, saying that the control number is yours when in fact it's from someone unknown. What we really mean by having 003 mandatory is '[ ] Mandatory for newly created records if 001 has a value', a checkbox which doesn't currently exist in frameworks and wouldn't be useful to add, since 003 is the only MARC21 field which is meaningless on its own and only exists as a prefix for another field. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.