In Koha, we have identified three scenarios that can create a Dual Status for an item in the Holdings table.
Scenario 1: The item is checked out to AND on hold for the same patron.
Reason: A Bug, sometimes associated with the SIP (4063), but other times just a bug..
In this instance, the item used to fill the hold has a restricted item type of Local Hold. It showed up on a pick list and was sent to fill the hold, even though it shouldn’t have (a bug).
Resolution: The hold will have to be manually removed from the patron’s account. Go their holds tab and select Delete or go to the Holds Priority list and change the hold from ‘Waiting’ to ‘Del’ (delete).
Scenario 2: The item is checked out to one patron and on hold for a different patron
Reason: An Item Level hold was placed for a patron by a staff member, instead of a Title Level hold. Patrons who place holds using the OPAC can only place Title Level holds.
Resolution: Remove the item level hold and replace it with a title level hold, that way the patron will get the Next Available item instead of waiting for one specific copy to fulfill their hold.
Scenario 3: The item is checked out to one patron and on hold for a different patron.
Reason: Simultaneous Holds Bug where Two copies of the same Title arrived for the same patron, but only one of the two is actually ASSIGNED to the patron to fill the hold and, when scanned at check in, prompted the Holds Conformation box (the other one, when scanned at check in, said “Not checked out.”)
Resolution: Check out the copy/item that triggered the Holds Confirmation to the Koha-assigned patron. Route the other copy back to the home library or scan it to see if it triggers another hold for transfer.
We understand that these scenarios and issues have been occurring more since December. All of these issues have been reported to our support vendor and several others have been reported to the Community, via Bugzilla.
Holds bugs and enhancements we are watching closely include:
- 2655 – Items on the Holds Shelf appear as “Available” in the OPAC (patches in 3.2, still some bugs)
- 2830 – Hold not removed when “trapped” item on hold shelf is checked out to a different patron in the holds queue (Critical, still open)
- 3270 – Canceling a hold request after transfer initiated orphans item (Major, still open)
- 3287 – Cancel Hold script makes unjustified assumption of Home Library return (Major, still open)
- 3288 – Transit prompt not immediately triggered after hold is canceled (Normal, still open)
- 3344 – Hold priority list needs additional status for items assigned but not waiting (Critical, preliminary patch)
- 3345 – Return All items on patron detail does not initiate transfer of holds (Normal, still open)
- 3536 – Checked In item requiring transfer does not consistently trigger transfer prompt (Patch sent 12-26-09)
- 3595 – Items seen at checkin should always go to 1st priority hold
- 3792 – Checking out on-hold item to someone else replaces item-level hold with next available (Jane wants a different behavior than we do, but still an interesting bug)
- 4063 – SIP Returns sometimes cause items to have dual statuses
- 4224 – Holds queue report includes items already allocated
- 4373 – Placing and Processing Items Simultaneously causes multiple issues