Bug 37609 - Item type code of 0 causes cascade of failure
Summary: Item type code of 0 causes cascade of failure
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-09 15:58 UTC by Esther Melander
Modified: 2024-08-09 15:58 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Esther Melander 2024-08-09 15:58:37 UTC
The general rule of thumb when creating item type codes is all capital letters, no spaces, no special characters. This implies that alpha numeric characters will work, including the number 0. However if an item type is created with a code of 0, it will cause various failures. I am assuming Koha is reading the number 0 as null or blank. If the number 0 cannot be used, documentation should include both best practices but also what should not be used like the number 0.

These are the failures I made note of:

1. An item can't be saved with the 0 item type in the 952$y or the 942$c, which also prevents circulation.
2. If a circulation rule is created with the 0 item type, the rule can't be deleted.

Deleting the 0 item type is the only way to remove the circulation rule.

I did some additional testing where I changed the Item Type code to '0A' and 'A0' and had similar results.