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

Description:
When creating the hold request, the recall type of 03 is simply supposed to place a hold on the item and not recall it (according to the v18 User Guide). This has been the case in previous versions, but we have noticed in version 18 that the item is recalled.

When processing this type of hold request, the 'Create Hold Request' window does not grey out the fields for Recall Due Date and Recall Due hour and once the recall type 03 request is processed, the item is automatically recalled and the due date is adjusted to whatever is entered in those fields.

We have additionally noticed that if these items are returned late, Aleph is assigning a rush recall overdue fee. It seems that that the recall type of 03 instead of placing a simple hold on the item is behaving like the recall type of 02 (rush recall).

Resolution:
The $alephe_tab/tab100 has ONLINE-RECALL=Y. Since the ONLINE-RECALL parameter is not included in the ABC50, this value of "Y" is in effect.

ONLINE-RECALL=Y is incompatible with the producation of hold requests. You need to change it to "N".

I am including an excerpt from the pc_server log, with my diagnostics, which shows that when the ONLINE-RECALL=Y, the z36 record is updated *first* -- with a recall-type of "01" and only later is the Z37, with the "corrected" type of "03" created....

DESCRIPTION: Create a New Hold Request - Item
ACTION : GET_RECALL
PROGRAM : pc_cir_c0419

Z36-REC-KEY= 002687470000010
Z36-ID= 0000181810
C0419-RECALL-TYPE= 01
io_z305_selected
io_z30
tab16_get
TAB16-RECALL-PERIOD= 007
ELAPSED-TIME: C0419 19:50:38 0.0073
...
<snip>
...
SERVICE : C0419
MODULE : Circulation Services
DESCRIPTION: Create a New Hold Request - Item
ACTION : PUT
PROGRAM : pc_cir_c0419

PUT Z37-RECALL-TYPE= 01
correct_z37 Z37-RECALL-TYPE= 03
ELAPSED-TIME: C0419 19:50:40 0.0694