Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Higher Fine and Notice for Requested Item Without Due Date Change

     

    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

     

     

    Desired Outcome Goal:
    Cause requested items to have a higher fine and to generate a patron notice about the higher fine if the item is not returned -- but NOT change the due date.

     

    Procedure:
    IMPORTANT: This solution works when tab100 RECALL-METHOD=1; it does NOT work if RECALL-METHOD=2] 

    If these have been defined as holds, they need to be defined instead as recalls. The due-date does NOT need to change. 

    1. Activate recall fines by setting tab18.lng > 0050 line > column 5 = Y (for rush recall, the 0051 line). 

    2. If tab100 has: 
    * OVERDUE-RECALL-RATIO=N, specify a flat amount in tab18 > column 6 
    * OVERDUE-RECALL-RATIO=Y, the number in tab18 > column 6 is a percentage and the regular overdue fine is multiplied by this amount in order to calculate the recall overdue fine. 

    3. Confirm that the tab16 > column 14 Fine-method includes recall.


    Additional Info / Related Articles    
    * When an item is recalled, a recall notice is sent to the patron. This notice informs the patron that someone else has requested the item. The form for these notices is ./form_lng/loan-recall-n-nn.xsl. A fine amount can be included in this notice. 

    * The batch job which prints these notices is p_cir_13. In order for a recall fine be in effect and for p_cir_13 to print a notice, the type must be 01. 

    * To generate the notice and the fine, and NOT shorten the due date: 

    1. change the www_server.conf > www_z37_recall_type from 03 to 01; restart the www_server. 
    2. change the GUI > Create Hold Request screen > default Recall Type from 03 to 01. 
    3. change the tab16 > column 19 value to 999; restart the pc_server.

     


    • Article last edited: 28-Feb-2016
    • Was this article helpful?