Description

I'd like to enable staff to perform renewals on Long Overdue items, but can't figure out how. Alternatively, is there a way to bulk renew a set of Long Overdue / Lost items behind the scenes?

(Context:  we'd like to renew all the items that have gone to Lost / Long Overdue since the start of March, due to the COVID-19 situation.)

Resolution

**Overdue item not yet LOST**

This is addressed in this article which was published a week or so ago (and sent to the Aleph user list):
https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/How_to_handle_due_dates_during_unexpected_library_closure

**Overdue item which has gone to z36_status LOST**

There are two aspects to this:

 a) the Services described in the above article operate only on z36_status "A" (Active); they don't operate on status "L" (Lost).

 b) when an item becomes LOST a Z31 Cash record is created for it. The xxx50 tab100 LATE-RET-FINE-WHEN-LOST parameter plays a role in this. (See https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/Overdue_fines_assessed_after_items_declared_lost%3B__LATE-RET-FINE-WHEN-LOST .)

I suggest the following (-- back up the z31 and z36 tables first and do it on the Test server first --):

1) Waive all LOST charges created between x date and the current:

 SQL> update z31 set z31_status = 'W' where z31_status = 'O' and z31_date_x > 'yyyymmdd' and z31_type in ('0040', '0041', 0042');

2) Change the z36_status of the affected loans from "L" to "A" and reduce the z36_letter_number:

 SQL> update z36 set z36_status = 'A', z36_letter_number = (z36_letter_number - 1) where z36_status = 'L' and z36_due_date >= 'yyyymmdd';

(where "yyyymmdd" is the first date that the library was closed due to COVID-19).

3) Follow the suggestions described in the above article ( https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/How_to_handle_due_dates_during_unexpected_library_closure ) to renew the items.

• Article last edited: 8-Mar-2018