https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27365
--- Comment #38 from David Cook <[email protected]> --- (In reply to Thomas Klausner from comment #23) > (In reply to Katrin Fischer from comment #19) > > Just a note here: the normal cataloguing editor does enforce a length, the > > input field shave maxsize = 9999 set (at least in MARC21). Is this different > > for UNIMARC? But if you import using staged import it's probably just being > > added as is. > > Using the latest KTD, I could enter data longer than 9999 bytes (even > ignoring chars vs bytes..) into eg 521$a, which does has a `max_length`. So > maybe the max length is ignored (another bug?). > > And even if it wasn't ignored, the length limit is per *field*, not per > *subfield*, so eg even if (521$a < 9999) && (521$b < 9999), 521$a + 521$b > could be greater than 9999 (triggering the bug) On 23.11.x and ktd, I don't see a maxlength attribute on textareas in the editor. If I add one via the browser HTML inspector, then copy and paste the text back in, then the text gets truncated according to the maxlength, and I can't add any more text. Although as Thomas says, since 9999 is a limit of the field rather than subfield, that isn't a perfect solution. That said, it would be an improvement. We could have Javascript or Perl that checks the aggregate of subfields for a field... But that could always be bypassed by using Staged MARC Import. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
