Bug 4242

Summary: Checkin damaged removes item from holds queue
Product: Koha Reporter: Jane Wagner <jwagner>
Component: Hold requestsAssignee: Jane Wagner <jwagner>
Status: CLOSED INVALID QA Contact: Bugs List <koha-bugs>
Severity: enhancement    
Priority: P1 - high CC: chris, julian.maurice, jwagner
Version: Main   
Hardware: All   
OS: All   
Change sponsored?: Sponsored Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:
Attachments: Screen shot if no other copies are available
Screen shot if other items are available

Description Chris Cormack 2010-05-21 01:24:50 UTC 


---- Reported by jwagner@ptfs.com 2010-02-22 20:18:40 ----

Sponsored by Middletown Township Public Library, Middletown, NJ, USA.

If an item's status is set to damaged while it is checked out, and there are existing holds on the item, checking the item in will not trigger the next hold.  Instead, a screen message will advise that there are holds waiting but the item is damaged.  If there are multiple items and others are available, a screen message says so; staff should retrieve one of the other items to trigger and fill holds.



---- Additional Comments From jwagner@ptfs.com 2010-02-26 20:10:50 ----

Created an attachment
Screen shot if no other copies are available





---- Additional Comments From jwagner@ptfs.com 2010-02-26 20:11:12 ----

Created an attachment
Screen shot if other items are available





---- Additional Comments From jwagner@ptfs.com 2010-05-12 13:57:23 ----

The fix for this bug (in ptfs-harley) can be pulled from the public git repository at http://github.com/Koha-PTFS, branch http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4242




--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:24 UTC  ---

This bug was previously known as _bug_ 4242 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4242
Imported an attachment (id=1931)
Imported an attachment (id=1932)

Unknown operating system Windows 2000. Setting to default OS "All".
Actual time not defined. Setting to 0.0
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here: chris@bigballofwax.co.nz.
   Previous reporter was jwagner@ptfs.com.
The original assignee of this bug does not have
   an account here. Reassigning to the default assignee
   for the component, gmcharlt@gmail.com.
   Previous assignee was kohaprogrammers@ptfs.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Bug reassigned, setting status to "NEW".
   Previous status was "ASSIGNED".
CC member jwagner@ptfs.com does not have an account here
The original submitter of attachment 1931 [details] is unknown.
   Reassigning to the person who moved it here: chris@bigballofwax.co.nz.
The original submitter of attachment 1932 [details] is unknown.
   Reassigning to the person who moved it here: chris@bigballofwax.co.nz.
Comment 1 Julian Maurice 2011-03-11 11:28:13 UTC 
There is no patch attached to this bug neither on mailing list.
Changing priority to P1.
Comment 2 Owen Leonard 2011-03-31 16:40:52 UTC 
> If an item's status is set to damaged while it is checked out, and there are
> existing holds on the item, checking the item in will not trigger the next
> hold.

I do not find this to be so:

1. Checked the item out to a patron.
2. Place the item on hold for a couple other patrons.
3. Set the item's damaged status.
4. Checked in the item.

I got the standard hold notification message. No message at all about the item being damaged.
Comment 3 Katrin Fischer 2011-03-31 16:48:34 UTC 
I wonder if this behaviour should be a syspref. Our libraries mark items damaged so people will not get charged for returning a damaged book. But it will not necessarily be replaced. Example: a book with water damage but still usable. The item should fill the hold like an undamaged item.