Bug 29101 - unable to enter 020 and 024 tag fields other than blank
Summary: unable to enter 020 and 024 tag fields other than blank
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: unspecified
Hardware: PC Linux
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
Depends on:
Reported: 2021-09-23 20:13 UTC by Courtenay Johnson
Modified: 2022-06-06 20:25 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:

Framework with problem, used for audio (3.88 KB, application/vnd.ms-excel)
2021-09-23 20:13 UTC, Courtenay Johnson

Note You need to log in before you can comment on or make changes to this bug.
Description Courtenay Johnson 2021-09-23 20:13:42 UTC
Created attachment 125222 [details]
Framework with problem, used for audio

KOHA version 18.11, Ubuntu 20.04.3


When cataloging a new audio item I get an error if the line for tag 20 or 24 are not blank. I am using a framework for audio items. When I used a framework for books earlier I did not encounter this problem even though I did enter a 13 digit ISBN for that title.

Tag "20" is not a valid tag. at /usr/share/koha/lib/C4/Biblio.pm line 2517.
Tag "24" is not a valid tag. at /usr/share/koha/lib/C4/Biblio.pm line 2517.

I can't have any number in the input field for 20 ISBN 13, or 24 for a 12 or 13 bit UPC or EAN. If both are blank then the save works. A subsequent edit also fails to save if either of these tag input fields are not blank.

Today I used 2 other frameworks, 1 for books and 1 for DVD/Video and I had no problem entering an ISBN value. 

I have exported the 2 different frameworks and can't see any differences for these tags.
Comment 1 David Cook 2021-09-23 23:21:19 UTC
This sounds like a support query rather than a bug report. 

I'd suggest trying the mailing lists, IRC, or a support company: https://koha-community.org/support/.
Comment 2 Courtenay Johnson 2021-09-24 23:32:20 UTC
Problem resolved. Update to 21.05 reported problem as error 500. Found by examining log and the file it pointed to the problems that the tag specified in the framework should be 020, and not 20. Ditto for tag 24 in the framework should be 024.