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

    Unwanted text from Aleph OPAC hold request being pulled through into Primo

    • Product: Aleph
    • Product Version: 21, 22, 23
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

    Description

    We offer item level requests. Some information is being pulled through from Aleph into Primo via OPAC via Primo which then shows in the pickup location menu that users are given for them to choose and confirm their hold request, e.g.:

    • Item is in the closed stacks.
    • Item is on an open shelf.
    • Item status: XX Call number: YY etc. 

     

    How can we disable this messaging in Aleph or change the fields that are being brought through so that the message users see on Primo makes more sense?

    Resolution

    These messages are usually initiated by xxx50/tab/tab_hold_request, mainly the INFO section. Quoting from the table's header: 

    ! - INFO is used when displaying the hold request fill-in form

     

    The texts of the messages are defined in $alephe_root/error_lng/check_hold_request, e.g. 

    !* check_hold_request_k 
    6010 L Item is in the closed stacks. 
    6011 L Item is on an open shelf. 
    6012 L Item status: $2 ($1) Call number: $3, $4 
    

     

    You can deactivate unwanted hold request checks in tab/tab_hold_request, or you can change their wording in error_lng/check_hold_request. The same change will be reflected both in Aleph Web Opac and Primo.


    • Article last edited: 16-May-2017
    • Was this article helpful?