Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Primo

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Primo
    3. Product Documentation
    4. Primo
    5. Interoperability Guide
    6. Configuring the Real-Time Availability Mapping Table
    7. Voyager Configuration

    Voyager Configuration

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    This information is not applicable to Primo VE environments. For more details on Primo VE configuration, see Primo VE.
    Return to menu
    Use the following table to configure the fields for the mapping_tables method:
    Real-Time Availability Mapping Table (Voyager)
    Parameter Description
    Enabled
    Select this box to enable this mapping row.
    Parameter 1
    This field defines the mapping to the Primo institution. The default mapping is subfield a, which means that the institution is based on subfield a of Voyager field availability field. Subfield a is defined in the Voyager extract. If your normalization rules use a different subfield, the default should be changed. It is possible to enter multiple subfields by entering them without a space (for example, ab for subfield a and b).
    The RTA program automatically uses the ILS Institution Codes mapping table to map the content of the Voyager subfield. If you do not use this mapping table in your normalization rules, consult Ex Libris support.
    Parameter 2
    This field defines the mapping to the Primo library. The default is subfield b, which is the Voyager owning library. If your normalization rules use a different subfield, the default should be changed. It is possible to enter multiple subfields by entering them without a space (such as ab for subfield a and b.
    The RTA program automatically uses the ILS Library Codes mapping table to map the content of the Voyager subfield. If you do not use this mapping table in your normalization rules, consult Ex Libris support.
    Parameter 3
    This field defines the mapping to the Primo sub-location. The default is subfield c, which is the Voyager location name. If your normalization rules use a different subfield, the default should be changed. It is possible to enter multiple subfields by entering them without a space (such as ab for subfield a and b). If you use a mapping table in the normalization rules, it is possible to define it after the subfields using a comma. For example:
    a,ILS Location codes
    Parameter 4
    This field defines the field in the Voyager record that contains the availability information (as defined in the Voyager extract for Primo). The default value is 949.
    Active
    Set this field to Y to activate RTA for Voyager.
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Aleph Configuration
      • Voyager Universal Borrowing
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Content Type
      Documentation
      Language
      English
      Product
      Primo
    2. Tags
      1. Configuring the Real-Time Availability Mapping Table
      2. contype:docum
      3. Interoperability Guide
      4. Prod:Primo
    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