Bug 25878 - Schema incorrectly describes course_items fields
Summary: Schema incorrectly describes course_items fields
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Database (show other bugs)
Version: Main
Hardware: All All
: P5 - low minor (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-25 16:20 UTC by Andrew Fuerste-Henry
Modified: 2020-08-30 19:34 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:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2020-06-25 16:20:21 UTC
On the schema page for the course_items table we include this comment on course_items.itype:
"new itemtype for the item to have while on reserve (optional)"

We have comparable notes for ccode, holdingbranch, and location.

That comment is not strictly correct. While a course is active, these fields in course_items will hold the items original values. If the course is marked inactive and the item's original values are returned to the items table, then the fields in course_items will hold the values that this item had while on reserve.

At this time I do not have alternate wording that explains this succinctly enough to put into the schema comment.
Comment 1 Katrin Fischer 2020-08-30 19:34:38 UTC
I believe this might have changed recently, as we have 3 columns now for each of the values that can be changed. Andrew, can you confirm?

`itype` varchar(10) DEFAULT NULL, -- new itemtype for the item to have while on reserve (optional)
`itype_enabled` tinyint(1) NOT NULL DEFAULT 0, -- indicates if itype should be changed while on course reserve
`itype_storage` varchar(10) DEFAULT NULL, -- a place to store the itype when item is on course reserve