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. Location duplicated in Primo because of duplicate AVA fields coming from Aleph

    Location duplicated in Primo because of duplicate AVA fields coming from Aleph

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share

     

    1. Description
    2. Resolution

     

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

     

    Description

    Two AVA fields are being generated for Aleph sys no 000013037 for the WBM location.  This causes it to be duplicated in Primo.  We don't want that.

     

    Resolution

    When the xxx01 tab_expand  expand_doc_bib_avail line being used for Primo has a "COLLECTION=Y" parameter (-- the recommended setting --), a separate AVA field is generated for each distinct Collection.

    In this particular case, items 000013037-10 to 000013037-40 have "z30_collection = RST" while items 000013037-50 to 000013037-70 have z30_collection = <blank>". 

     


    • Article last edited: 1-Sep-2017
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Location display twice in Brief View in OPAC for serials with subscriptions
      • Location in Web Holdings Item detail has $i and $j reversed.
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Alma Specto
    2. Tags
      1. contype:kba
      2. Prod:Aleph
    1. © Copyright 2026 Ex Libris Knowledge Center
    2. Powered by NiCE Knowledge Management ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved