• Article Type: General
• Product: Aleph
• Product Version: 20
• Relevant for Installation Type: Dedicated-Direct; Direct; Local; Total Care

For QRS50, we have cases where hold requests are made on Primo on available items. This should not happen.

Here are 2 cases.
Item 000004253000030 was returned on 20111215 and next loan was on 20120105.
But it was requested on 20120103.

Item 000007233000030 was returned on 20111217 and next loan was on 20120105.
Looking at z37(h), last request was on 20071004.
But looking at gui circ, E00843343 is requested to user QRS-32051.
Back to Z37, I see that QRS-32051 requested 000007233000010. (10 instead of 30, but E00843343 should be 30 based on gui "Seq" in items list).

What's happening?

Resolution:
The check_hold_request type which prevents holds from being placed on available items is check_hold_request_g.   If tab15.lng col. 8 = "Y" and the patron's z305 (Local Patron) record has Z305-HOLD-ON-SHELF = "N", the hold can be placed only if the item is unavailable.

In qrs50 tab_hold_request there is no check_hold_request_g for HL-GRP (the label used for PRIMO). This needs to be added and the www_server restarted.

Category: Circulation

• Article last edited: 10/8/2013