Summary: | MARC frameworks should validate subfield code when adding new subfields | ||
---|---|---|---|
Product: | Koha | Reporter: | Esther Melander <esther.melander> |
Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | m.de.rooy, magnus |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Esther Melander
2024-05-02 19:41:23 UTC
I think subfield codes/names/identifiers are always limited to one character? "Subfield codes - Two characters that distinguish the data elements within a field which require separate manipulation. A subfield code consists of a delimiter (ASCII 1F hex), represented in this document as a $, followed by a data element identifier. Data element identifiers may be a lowercase alphabetic or a numeric character." https://www.loc.gov/marc/bibliographic/bdintro.html Yes, and the database field is only one character too, which is why it gets cut off. I think we could do with better validation. Koha kinda supports uppercase letters, we have been using them for years now for some extra information. |