| Summary: | Items available for hold or loan must have an item type | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Barton Chittenden <barton> |
| Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED FIXED | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | andreas.jonsson, m.de.rooy |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Crowdfunding committed: | 0 |
| Crowdfunding contact: | Patch complexity: | --- | |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Barton Chittenden
2018-09-28 19:36:47 UTC
If the problem is acq items, maybe setting the itemtype not-mandatory for the ACQ framework but mandatory for every other would work? There is a lot more things that influence if an item can be checked out, not only the not-for-loan status. (In reply to Katrin Fischer from comment #1) > If the problem is acq items, maybe setting the itemtype not-mandatory for > the ACQ framework but mandatory for every other would work? There is a lot > more things that influence if an item can be checked out, not only the > not-for-loan status. I'm not sure that will work: 1) If item-level_itypes is set to 'biblio record', items.itype may not be set at all, so we really need to test that one or the other is set. 2) Even if an item is in acquisitions, the library may want to the not-for-loan status to a negative number, making it available to be placed on hold... at that point, the item type needs to be set. That may well happen while the item is still in acquisitions. Also, frameworks are editable, and I'd rather not have this be something that a user can disable. We are now enforcing the itemtype to be mandatory. |