Summary: | Allow/Don't allow holds on items with set statuses | ||
---|---|---|---|
Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
Component: | System Administration | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | gmcharlt, marjorie.barry-vila |
Version: | unspecified | ||
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: |
Description
Christopher Brannon
2014-10-15 21:12:59 UTC
I think in general that would have been a great idea, but I am worried that migration now would be too hard. Also there are some specific NFL and LOST values tied to features in Koha. Then perhaps we do away with the negative value/hold relationship in NOTFORLOAN, and a new setting created to list what statuses allow holds? NOTFORLOAN: 1,2,5 DAMAGED: 2,5 LOST: 3 I think settings would work, yes. Also this would allow for migrations without changing behaviour. (In reply to Katrin Fischer from comment #3) > I think settings would work, yes. Also this would allow for migrations > without changing behaviour. :) I finally have an idea you like! :) Just kidding. I know you are trying to keep us in line with what everyone else is doing. Thanks for helping us with the perspectives. |