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. Is it possible to display specific reasons for non-renewable items in OvP (after 22.1 rep_change 2042) after renew all?

    Is it possible to display specific reasons for non-renewable items in OvP (after 22.1 rep_change 2042) after renew all?

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Description
    2. Resolution
    3. Additional Information
    4.  

     

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

     

    Description

    In file ./xxx50/tab/tab_check_circ option RENEW-PRE parameters are used, so that the patron knows if he can renew his documents in "My account" (OvP) 

    ex. 
    RENEW-PRE check_circ_1_c_a 
    RENEW-PRE check_circ_3 
    RENEW-PRE check_circ_5_b 
    RENEW-PRE check_circ_6 
    RENEW-PRE check_circ_7_b 

    If documents are not renewable, the patron sees "renew not possible" under the "Status" column, which is a general message. Is there a way to use RENEW-PRE parameters AND display the specific reasons why the documents could not be renewed in Primo?

    Resolution

    No, it is not possible; 
    changing this behaviour means a major design change in Primo and Aleph as Primo would need to try renewal even for non-renewable items. 

     


     

    Additional Information

    Aleph 22, rep_change #002042 has enhanced two programs:

    ./alephm/source/dlf_service/dlf_single_renew_loan.cbl (Single renew)
    ./alephm/source/dlf_service/dlf_renew_loan.cbl (Renew all)

    - dlf_single_renew_loan is a subroutine called from dlf_renew_loan.
    - dlf_renew_loan uses RENEW-W-G from tab_check_circ and dlf_single_renew_loan uses RENEW-WWW.

    There is a slight discrepancy in the design of the Aleph OPAC and the design of the Primo-Aleph API causing a different behavior when "renew all" is called up.

    In Aleph OPAC there is a separate program routine for renew all that displays specific reasons.

    In RESTFUL API only one API for renewal exists (https://developers.exlibrisgroup.com...PIs/Renew-Loan) and this API is used for both single renewal and multiple/all renewal.

    For all items "non-renewable" by the RENEW-PRE-checks, Primo will not attempt to perform renewal when the patron tries to "renew all" (as it knows that renewal will fail anyway). Therefore also after this rep_change no specific renewal problems are displayed in this case.


     

     


    • Article last edited: 5-Apr-2016
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Is it possible to delete the contents of /exlibris/ftp_from_exlibris/ ?
      • Is it possible to eliminate sip2 patron information response ("Patron in file")?
    • 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