p_item_11 leaves expired hold requests

• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
I've been working with p-item-11 to batch delete some old temporary item records. I'm noticing a problem similar to the one I reported in KB 16384-2707 .

Many of these items had hold requests, which were beyond their end date. These holds were not detected by the batch process, and the items were considered valid for deletion. I ran it with update database set to Y and those items were deleted. But the z37 records are still there.

Viewing a patron's record lists the request, but it's not accessible because the item has been deleted.

Can this service be updated so that either expired requests are detected and prevents deletion of the item, or they are detected and deleted along with the item.

I am now looking for the batch service that will find and delete these hold requests.

Resolution:
p_cir_17 deletes expired hold requests and p_cir_06 deletes requests beyond their end hold (shelf) date.

If you precede each run of p_item_11 by runs of p_cir_06 and p_cir_17, you will not see this problem.

• Article last edited: 10/8/2013