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

Description:
Our 4 hour loan items (item status 25) are not going into Long Overdue status (Lost) when they should be according to tab32 (1 day past due). Please see patron account 39260, item barcode 39031026593871. This item was due on Nov 16 and should have been set to Long Overdue (Lost) by Nov 18. We run p_cir_50 to send out the Bills for our Long Overdue items.

Resolution:
The z36 for item 002912867-000080, on loan to patron 39260, has:

02 z36_item_status .............25
02 z36_bor_status ..............08


Checking the abc50 tab32, we see this:

##### 25 ## 00 001 001 O 0080
##### 25 ## 02 001 001 L
##### 25 ## 09 002 002 L

This means that a first (overdue) notice will go out the day after the item becomes overdue. The "25 ## 02" line would be used in the case where the item has had 2 notices sent and this would be the third notice.

But it will never get to the "25 ## 02" because there is no "25 ## 01" line. (It will be looking for a "25 ## 01" line and never finding it, so it will do nothing.)

But you say you want these items to go into Long Overdue status (Lost) when they are 1 day past due.

It seems to me to do that you need the following tab32 lines:

##### 25 ## 00 001 001 L
##### 25 ## 09 002 002 L

• Article last edited: 10/8/2013