Summary: | In Advanced Editor mandatory subfields are not enforced if tag is not mandatory | ||
---|---|---|---|
Product: | Koha | Reporter: | Andrew Fuerste-Henry <andrew> |
Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | bwsdonna, dcook, m.de.rooy, mathsabypro, phil |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26055 | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Andrew Fuerste-Henry
2020-07-08 20:50:22 UTC
Agreed This is still an issue as of 23.05 and is very confusing. And since the mandatory field (100$a in this example) does not even display in a new record in advanced editor, but then immediately triggers an error when saving in basic editor, it causes issues when staff are adding new records. Perhaps even just adding a note that it must be marked mandatory in order to display in advanced editor? On the other hand, in bug 32722 UNIMARC wants the exact opposite, to have the current behavior of the advanced editor be the behavior of the basic editor, because they have subfields that are mandatory if any other subfield of the tag is used, but having the tag is not mandatory. 100$a is actually a perfect example of the use-case for that: although MARC21 doesn't have the concept of required subfields, a personal name without a name is meaningless (and awkward to deal with if you autocreate an authority from it), while a bib record without a personal name as the main entry is very common, so it would be convenient to be able to require that $a be non-blank if 100 is used at all, but not require that it be used. |