Summary: | Data inconsistencies - "Item type" and "item type for older issues" in subscriptions | ||
---|---|---|---|
Product: | Koha | Reporter: | Victor Grousset/tuxayo <victor> |
Component: | Command-line Utilities | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | robin |
Version: | Main | ||
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: | |||
Bug Depends on: | 20461 | ||
Bug Blocks: | 21010 |
Description
Victor Grousset/tuxayo
2018-08-23 15:12:50 UTC
This issue is one of the causes of having invalid itype on items. So it would help having directly the root cause. We use a check for that: https://git.biblibre.com/biblibre/tools/src/commit/da516fdcd8a367047e1a5e5bdff9f9449f45b6eb/koha/db_check_itype.sh#L34 The important par is this one: if [[ "$itype_on_item" ]] && # the syspref [[ "$makePreviousSerialAvailable" ]] && # another syspref [[ "$invalid_itemtypes_exists" || # subscription.itemtype "$invalid_previousitemtypes_exists" ]] # subscription.previousitemtype Maybe checking for subscription.itemtype isn't need. I haven't tested if the MARC frameworks usually doesn't let invalid values slip by. |