Summary: | Circ restrictions caused by long overdue should be removed when the offending item is returned | ||
---|---|---|---|
Product: | Koha | Reporter: | Nick Clemens (kidclamp) <nick> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | andrew, cslone, dstephen, george, gmcharlt, kyle.m.hall, lisettepalouse+koha, magnus, michaela.sieber, robbinsk |
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: |
Description
Nick Clemens (kidclamp)
2016-07-08 15:38:48 UTC
I agree it would make sense to be able to tie a restriction to a specific on loan item, and then remove that specific restriction when the item is returned. We encountered this issue yesterday. Patron returned a long overdue item but the restriction was not removed because she had another item out that was one day overdue. I think the restriction should be removed as long as all of the patron's long overdue items have been returned. The ODUE restriction is set by sending out a notice x days after due date. I think we could check the due dates of the other items on lifting the restriction maybe. Running into a similar thing that perhaps needs to be a different bug(?), but the restriction is also not lifted if the charge for the long overdue/lost item is paid or written off. The restriction has to be manually removed. We are also having this problem. Our restricted patrons are returning items but the restriction must be removed manually. Our patrons are restricted from checking out if a single item is 7days past due. Upon return the restriction should be removed automatically. The bug is keeping patrons from using our self checks. +1 here, I've spoken to many libraries that would prefer the restriction be specific to the item(s) that triggered the notice. This could be a new syspref tied to AutoRemoveOverduesRestrictions so it asks: "(Do / Do not) allow OVERDUES restrictions triggered by sent notices to be cleared automatically when (all / triggering) overdue items are returned by a patron." Another +1 on here now that I'm working in a library that would like for overdues restrictions to clear based on *triggering* overdues rather than all overdues. (In reply to Andrew Fuerste-Henry from comment #6) > +1 here, I've spoken to many libraries that would prefer the restriction be > specific to the item(s) that triggered the notice. This could be a new > syspref tied to AutoRemoveOverduesRestrictions so it asks: "(Do / Do not) > allow OVERDUES restrictions triggered by sent notices to be cleared > automatically when (all / triggering) overdue items are returned by a > patron." |