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

Description:
Our technology items (item status 08 and 25) are not currently going into lost status. In December I changed tab32 to skip sending any overdue notices for item statuses 08 & 25 and just declare the item lost on the day after it's due.

This setup failed and none of these items went into the Lost status.

The day before yesterday I changed the table back to send out 1 overdue notice and to have the items be set to Lost the next day. Yesterday the overdue notices went out, but today nothing was set to Lost as expected.

Please see item 39031028078830 checked out to patron id 251686 as an example of something that should have been declared lost but wasn't.

Resolution:
Checking in the $alephe_scratch directory, I don't find any runs of p_cir_50 or p_cir_51 for p_letter_type "L":

>>aes
>>grep 'p_letter_type "L"' *cir_51*
>>

("L" prints Lost notices/bills, looking through tab32 for "L" lines; "O" prints Overdues.)

(I *do* find numerous runs for 'p_letter_type "O".)

See KB 8192-4557 for a complete discussion of overdue notice logic.

• Article last edited: 10/8/2013