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

    Does new Voyager location impact Primo Extracts?

    • Article Type: Q&A
    • Product: Voyager
    • Product Version: 8.0.0

    Question

    A new location code has been added to SysAdmin. Does this affect the extracts for Primo?

    Answer

    * If the location is OPAC suppressed, there is no change to the Primo extract.
    * If new location code will be viewed in Primo, the code must be added to the Primo extracts config files only if the [LocationCodesForBibInclusion] in PrimoExp*.ini files are NOT blank. If the stanzas are blank, no changes are needed.

    Additional Information

    Related articles:
    Add a New Location to Voyager
    Add New ILS Location to Primo Library Codes

    How to check the PrimoExp*.ini files:

    1. In m1/voyager/xxxdb/ini, find the most recent PrimoExp-*.ini files. There will be files for PrimoExp-Selective.ini and PrimoExp-Publishing.ini. (A consortia would have multiple versions of these files to be checked.)
    2. more PrimoExp-Publishing.ini
    3. Look for the stanzas [LocationCodesForBibInclusion] and [LocationCodesForAVA]
      1. If these stanzas are blank, no change is required.
      2. If these stanzas have locations codes AND the new code should appear in Primo
    4. Create an archive of the current version of the *.ini
    5. Add the new code to both stanzas and a comment to the top of the ini documenting the change.
    6. Save the changes.
    7. Make the same changes to PrimoExp-Selective.ini.
    8. Go to /m1/voyager/xxxdb/tomcat/vxws/ini/PrimoExp.ini. This file controls returned values for RTA.
    9. Look for the stanzas [LocationCodesForBibInclusion] and [LocationCodesForAVA]
    10. If these stanzas are blank, no change is required.
    11. If these stanzas are not blank, make the same changes as documented in steps 4-6.

    Category: Interoperability


    • Article last edited: 1/7/2015