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

Description:
After doing some work recently on our overdue notices, we discovered that hold requests have been triggering recalls for many years, even though none of our circ tables are set up to allow recalls.

The hold request generates a recall, that then gets submitted and printed as an overdue. I am attaching a copy of an example where an item is showing up as overdue even though it is many months before the due date.

Resolution:
The problem is the following setting in the $alephe_root/www_server.conf:

setenv www_z37_recall_type 01

"01" is recall. If you just do holds, you should have this instead:

setenv www_z37_recall_type 03

• Article last edited: 10/8/2013