Does new Voyager location impact Primo Extracts?
- 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
See also: Add a New Location to Voyager
How to check the PrimoExp*.ini files
- 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.)
- more PrimoExp-Publishing.ini
- Look for the stanzas [LocationCodesForBibInclusion] and [LocationCodesForAVA]
- If these stanzas are blank, no change is required.
- If these stanzas have locations codes AND the new code should appear in Primo
- Create an archive of the current version of the *.ini
- Add the new code to both stanzas and a comment to the top of the ini documenting the change.
- Save the changes.
- Make the same changes to PrimoExp-Selective.ini.
- Go to /m1/voyager/xxxdb/tomcat/vxws/ini/PrimoExp.ini. This file controls returned values for RTA.
- Look for the stanzas [LocationCodesForBibInclusion] and [LocationCodesForAVA]
- If these stanzas are blank, no change is required.
- If these stanzas are not blank, make the same changes as documented in steps 4-6.
- Article last edited: 07-Jan-2015