Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. Why does check_1_b not allow renewal in OPAC?

    Why does check_1_b not allow renewal in OPAC?

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Description
    2. Resolution
    3. Additional Information
    • Product: Aleph
    • Product Version: 21,22,23
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

     

    Description

     

    The patron has a local block '06' which should allow renewal, but the renewal is nevertheless blocked in OPAC. Why?

     

    ./xxx50/tab/tab_delinq.lng 

     

    !  2   3         4         5          6
    !          abcdefghi
    !!-!-!!!!!-!!!!!!!!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>

    06 2 ##### NNNNNN N        L all blocked, Renewal allowed

     

    ./xxx50/tab/tab_check_circ 

     

    RENEW-WWW  check_circ_1_a
    RENEW-WWW  check_circ_1_b
    RENEW-WWW  check_circ_1_c_a
    RENEW-WWW  check_circ_1_c_b
    RENEW-WWW  check_circ_1_e
    RENEW-WWW  check_circ_1_f
    RENEW-WWW  check_circ_2_a

    RENEW-WWW  check_circ_2_b

     

    Resolution

    Remove check_circ_1_b from ./xxx50/tab/tab_check_circ.

    If you would like to check the renew permission of the patron, use check_circ_2_b instead.

     

    Additional Information

    The header of ./xxx50/tab/tab_check_circ has the following explanation:

     

    !  1_b: patron blocks 
    !       Z305 
    !       Warning according to parameters as set in tab_delinq.lng  
    !       Note that Block Code "00" (col. 1 of tab_delinq.lng)  
    !       - displays no warning.
     

     

    That means, that if check 1_b is activated, the system will block any activity for patrons with local blocks other than '00'.

    Check 1_b does not take individual setup of table tab_delinq.lng into account.

     

    Other checks for local permissions, e.g. 2_a or 2_b allow the check of individual permissions set in tab_delinq.lng.

     

     

     


    • Article last edited: 07-Mar-2017
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Why does aleph_start.private QUE_STARTUP_LIBS line include "$QUE_STARTUP_LIBS"?
      • Why does p_cir_23 with Update not delete patrons and run so long?
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      This page has no tags.
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved