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

Description:
When the TAB100 RECALL-TYPE is "2", if an item that has been renewed is recalled, and the recall is later canceled, the due date jumps back to the original due date from the initial loan, and the patron suddenly accumulates months of overdue fines -- but it had been renewed and the book may not be overdue at all.

Resolution:
The ./butil/b_cir_13_reset_due_date program has the following logic:

EVALUATE TAB100-RECALL-METHOD
WHEN "1"
MOVE Z36-ORIGINAL-DUE-DATE TO Z36-DUE-DATE
WHEN "2"
CONTINUE
WHEN "3"
CONTINUE
WHEN OTHER
MOVE Z36-ORIGINAL-DUE-DATE TO Z36-DUE-DATE
END-EVALUATE.
...
EXIT-RESET-DUE-DATE.

Thus, when TAB100-RECALL-METHOD = 2 or 3, the program does *not* set the due-date back to the original due date. (It doesn't *need* to because, with these RECALL-METHOD's, the z36_due date is already the "due-date-before-recall" and includes any renewals that have occurred.)

• Article last edited: 10/8/2013