1. Voyager Extract for Primo May 2014
Good day everyone.
Today we’re going to be discussing Voyager data extracts for Primo.
My name is xxx. I’m a Primo Project Manager here at ExLibris.
I’ve been a project manager for Primo for xxxxx now – and for 10 years prior to that I worked in Voyager Support in a variety of roles.

2. Copyright Statement and Disclaimer
All of the information and material, including text, images, logos and product names, is either the property of, or used with permission by, Ex Libris Ltd. The information may not be distributed, modified, displayed or reproduced – in whole or in part – without the prior written permission of Ex Libris Ltd.
TRADEMARKS Ex Libris, the Ex Libris logo, Aleph, SFX, SFXIT, MetaLib, DigiTool, Verde, Primo, Voyager, MetaSearch, MetaIndex and other Ex Libris products and services referenced herein are trademarks of Ex Libris, and may be registered in certain jurisdictions. All other product names, company names, marks and logos referenced may be trademarks of their respective owners.
DISCLAIMER The information contained in this document is provided on an "AS IS" basis for general information purposes only without any representations or warranties, whether express or implied, including any implied warranties of satisfactory quality, completeness, accuracy or fitness for a particular purpose.
Ex Libris, and its subsidiaries and related corporations disclaim any and all liability for use of this information, even if advised of the possibility that loss, damage or expenses may arise.
© Ex Libris Ltd, 2014

3. Ground Rules Please note that everyone is muted upon entry Seeing?
Having
problems
Seeing?
with
Hearing?
Please let us know…
Ground Rules
Send us a message via chat

4. Today’s Agenda Voyager Extract for Primo Extract Types
Voyager Directory Structure & Files
What’s configured
Breakdown of .ini File(s)
Manually Running Extract(s)
Extra Logging
Review
Demonstration
Automating Extract(s)
Excluded Records
Other Resources
In today’s Voyager Extract for Primo training, we’ll be covering the following topics:
The 3 types of Voyager extracts for Primo
The Voyager Directory Structure & associated Files
What we configure for the extracts
The Breakdown of the Primo export initialization files – or the .ini files
How to manually Run Extract
How to do some easy Extra extract Logging
We’ll do a brief Review
A live Demo of the Voyager Selective extract
How to Automate your Extract(s)
Why Primo Excludes Records
What’s New in Voyager 9 for the extract – add later
And finally – what Other Resources you have available to besides this training for the Voyager Extract for Primo

5. Voyager Extract for Primo
Primo discovery takes advantage of the rich data stored in the Voyager database.
Bibliographic data is extracted from the Voyager database for an initial load and then, subsequently kept current via regularly scheduled updates with Primo.
The extract creates a single MARC XML record for each appropriate bib and its related records: holdings, items, authorities, course reserve info, and e-items
The Voyager extract for Primo creates XML files for export that conform to the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) schema.
So let’s talk a little about Voyager data in terms of Primo and how it all works:
Primo discovery takes advantage of the rich data stored in your Voyager database.
Your Bib data is extracted from the Voyager database for an initial load and then, subsequently kept current via regularly scheduled Voyager extracts and imports into Primo.
It’s important to note the difference between how the data lives in Voyager and how it lives in Primo
The extract creates a single MARC XML record for each appropriate bib and its related records: holdings, items, authorities, course reserve info, and e-items* (e-items were newly added into Voyager 8).
And of course, we follow the industry standards – so The Voyager extract for Primo creates XML files for export that conform to the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) schema.

6. Selective Extract Publishing Extract Availability Extract
3 Extract Types
Used for sample record sets, initial full extracts, and specific records; it is not used for daily extracts
Selective Extract
Used for ongoing extract (i.e. after initial full extract and load), ongoing/daily record updates
Publishing Extract
Used for availability extracts, several times daily
With RTA and web services, it’s not really used any longer
Availability Extract
So there are 3 different types of Voyager extracts for Primo…
There’s the Selective Extract
This is Used for sample record sets, initial full extracts, and specific records; it is not used for daily extracts
Our demo later will consist of a selective extract
The second type of extract is the Publishing Extract
This is Used for ongoing extracts – basically after your initial full extracts and loads occur, and you’re ready for ongoing/daily record updates
And finally there’s the Availability Extract
This is Used for availability extracts and is run several times daily
It’s important to mention that with OvP, RTA and the various web services, it’s not really used any longer
It’s was used before on-the-fly communication between Voyager and Primo was available
Customers would run the availability extracts throughout each day to continually update Primo
It’s great the progress that’s been made with the interoperability between Voyager and Primo

7. Voyager Directory Structure & Files
/primo
/Selective, /Publishing
/exports
temporary holding space for extracted records
/bundled
records wrapped into tar.gz files.
/logs
daily log file -- primo.export log
So let’s talk a little about the Voyager directory structure and the files used for the Primo extract
So everyone here is probably is probably familiar with the standard Voyager directory structure of /m1/voyager/xxxdb/
But we’re going to be looking at a few new places and some old familiar places in the Voyager directory structure and see the files necessary for the extract to run successfully.
The first place is the Primo directory – note that it’s a lower-case “p”
This is located in /m1/voyager/xxxdb/primo
Within that directory, you’ll see 3 subdirectories: Selective, Publishing, and Availability
These extracts relate to the 3 different extract types of you have available on your server
In each of these directories, you’ll see the following 3
The /exports directory
This is essentially a temporary holding space for extracted records – it’s no longer after Voyager 8 due to how we bundle records now
Then we have The /bundled directory
This is where records live that are wrapped into tar.gz files – Voyager uses a background script called PbundlePrimo that does the bundling
*This bundling process was eliminated in Voyager 8 where this process now happens on-the-fly. But you still have the exports directory left as reminder of days past
And finally, we have the /logs directory
This is where daily log files live
And the log file names look something like this -- primo.export log
Sample path: /m1/voyager/xxxdb/primo/Selective/bundled

8. Voyager Directory Structure & Files
/sbin Directory (scripts/programs)
/m1/voyager/xxxdb/sbin
Pprimoexp.sel (Selective)
Pprimoexp.pub (Publishing)
/ini Directory (initialization files)
/m1/voyager/xxxdb/ini
PrimoExp-Selective.ini
PrimoExp-Publishing.ini
OK – so let’s talk about some directories that you are probably very familiar with – the /m1/voyager/xxxdb/sbin and the /m1/voyager/xxxdb/ini directories
So your /sbin Directory contains Voyager’s scripts/programs
In this directory, you’ll see the following 3 scripts:
The Pprimoexp.sel for running the Selective extract
The Pprimoexp.pub for running the Publishing extract
So we run the programs or scripts in the SBIN directory – but we also need to use some initialization or configuration files for the extract as well.
These live in the /m1/voyager/xxxdb/ini directory
And just there are 3 scripts, there are 3 initialization files
PrimoExp-Selective.ini
And PrimoExp-Publishing.ini
So there are 3 scripts/programs, associated initialization files – and all are names to match the type of extract you’ll be running

9. What’s configured?
Item statuses to check for initial load and ongoing updates to the Primo database
Happening locations for exclusion
Operator ID - Records to be excluded from the initial load and/or ongoing updates based on last processing operator ID
Institution ID to be included in the availability tag
Location definitions for consistency within the Primo database
Tags to identify unique field usage within your institution’s database specific to the database extract
Extract processing considerations such as date/time, record ID(s), filters, etc.
Additional processing considerations for uploading the Voyager records identified by the configuration file processing
So here’s where we are going to get into the actual configurations that you can make when doing the extracts
When we look at the initialization files, we’re going to see many options available.
What are these options for?
Here’s a few things that can be configured in the INI file:
Item statuses to check for initial load and ongoing updates to the Primo database
Happening locations for exclusion: Records associated with these happening locations are excluded from the initial load and/or updates for Primo harvesting.
Records to be excluded from the initial load and/or ongoing updates determined by operator ID that processed the record
Institution ID to be included in the availability tag
Location definitions for consistency within the Primo database
Tags to identify unique field usage within your institution’s database specific to the database extract
Extract processing considerations such as date/time, record ID(s), filters, etc.
And finally, Additional processing considerations for uploading the Voyager records identified by the configuration file processing
We’re going to look more closely and review the entire ini file – so you can see what’s in there, what your options are, and how to configure them

10. .ini File Breakdown
All three .ini files are actually the same file with different lines being in/active
PrimoExp-Selective.ini
PrimoExp-Availability.ini (not used)
PrimoExp-Publishing.ini
There are a total of 12 stanzas in each .ini file (as of Voy 9)
Item Statuses, Excluded Happening Locations, Excluded Operator IDs, LocationCodesForBibInclusion, LocationCodesForAVA, LocationSortOrder, Institution ID, Location to Primo, Enrichment Tags, DPS, PrimoExp, & XML Writer Protocol
The .ini files are annotated with instructions on what needs to be filled out in the file as well as what type of data will or will not be extracted.
So as I mentioned there are 3 files in the INI directory
PrimoExp-Selective.ini
PrimoExp-Publishing.ini
And of as of Voyager 9 there are 12 stanzas in each ini file (I’m not going to read them since we’re about to look at all of them starting with the next slide).
And I should mention here – don’t be alarmed, each INI file is exactly the same – they each just have different sections commented out, so if you understand 1 INI file, you’ll understand how to configure all of them
And even better, is that the INI files are annotated with instructions on what needs to be filled out in the file as well as what type of data will or will not be extracted. Pretty handy!
So let’s jump into looking at an INI file now…

11. [Item Statuses] Stanza
Identifies which item statuses in Voyager are defined as Available (A) or Unavailable (U) for Primo’s purposes
Item status availability (A/U) can be changed
Ex: change damaged or “in transit” from U to A to show as available in Primo.
The first stanza in the INI file is the [Item Statuses] stanza.
The [Item Statuses] stanza identifies which item statuses in Voyager are defined as Available (A) or Unavailable (U) for Primo’s purposes.
Please note that the default settings here were created based on the un/availability distinctions in Voyager.
The item status can be changed, for example, so that damaged items or items that are “in transit” show as available in Primo.
But this is only a label change.
If you make an item show as available – and Voyager does not consider it available, it will have an affect (like in requesting).
I seriously encourage everyone to leave these options the way they are currently set up to avoid any issues.

12. [Excluded Happening Locations] Stanza
Identify records associated with these locations to be excluded from consideration for uploading to the Primo database
Location codes are defined in Voyager SysAdmin AND set as a work location (circ, acq or cat desk) in a Policy Definition
(Locations listed are samples only are commented out by default)
The second stanza is the [Excluded Happening Locations] stanza.
The [Excluded Happening Locations] stanza is used to identify the records associated with the specified locations to be excluded from the extraction.
The location codes are those that are defined in Voyager SysAdmin – basically the location codes – or what is used in the MFHD 852 subfield b.
The locations you see in the INI file are only there as an example and should be commented out by default.
Feel free to remove the commenting to use these examples and/or delete any that do not apply to your library and enter your own location codes.
NOTE: Only one location code may be entered per line.
Remove the commenting to use these examples and/or delete any that do not apply to your institution and enter your own location codes.
NOTE: Only one location code may be entered per line.

13. [Excluded Operator IDs] Stanza
Identifies the records associated with operator ID(s) to be excluded from consideration for uploading to the Primo database.
Enter one operator ID per line.
Great option to use when training new staff who may be updating Voyager records for practice
The third stanza is the [Excluded Operator Ids] stanza
This stanza is used to identify the records associated with these operator ID(s) to be excluded from consideration for uploading to the Primo database.
This is a great option to use when training new staff who may be updating Voyager records for practice.
And similar to the excluded locations option, you need to enter only one operator ID per line.

14. [LocationCodesForBibInclusion] Stanza
Lists specific 852b locations for extraction
Used for institutions that share a single Voyager database with one instance of Primo installed or institutions with a single, multi-clustered Voyager database
Provide a list of MFHD location codes whose attached bibliographic records should be extracted for Primo.
This is based on the 852‡b of any attached MFHDs
If you are considering using the [LocationCodesForBibInclusion] stanza,
please consult the Voyager® Primo® Integration User’s Guide
for more information about this option.
This next stanza is the [LocationCodesForBibInclusion] stanza.
I’m not going to get into the nitty gritty of it – but it’s important to understand the purpose of it – and from there you can determine whether or not this is something you should consider.
The [LocationCodesForBibInclusion] stanza is used to identify the records of specific locations for extraction. This may be useful for institution
that share a single Voyager database with one instance of Primo installed or institutions with a single, multi-clustered Voyager database.
Here’s my little story about this…
I had 2 customers who were in a shared Voyager database. This database was very large and contained every state university (and I should mention they were set up as a single owning library . But only two of the libraries in the database purchased Primo. Before this [LocationCodesForBibInclusion] option was available, we needed to extract all records from the Voyager database and then use the Primo normalization rules to try and sort out the different sites – which is what we did for the situation I just mentioned. Should this new option be available then, we would have only extracted the data from the 2 libraries – based on their location codes.
This stanza just needs a list of MFHD location codes whose attached bibliographic records should be extracted for Primo.
This is based on the 852‡b of any attached MFHDs.
And please, if you rte considering using this option, you should check with your Project Manager to be sure.

15. [LocationCodesForAVA] Stanza
Used with [LocationCodesForBibInclusion] stanza which identifies bibs
Used to identify other information to include with bibs extracted
Include 852b and item location codes (plus and UB location codes, temporary location codes, etc) which might exist in your records.
If you are considering using the [LocationCodesForAVA] stanza,
please consult the Voyager® Primo® Integration User’s Guide
for more information about this option as it explains Item Permanent & Temp locations, Reserve Locations, etc.
The [LocationCodesForAVA] stanza is used in combination with the [LocationCodesForBibInclusion] stanza that we just discussed.
Once your list of extracted bibliographic records has been identified (based on location), the process also needs to determine what information should be included in the extracted record.
Again, should you be considering this option, please check with your Project Manager.

16. [LocationSortOrder] Stanza (Voyager 9)
#Indicate how locations in the availability statements should be sorted
# when displayed in Primo. The following example shows the location # main is ranked 1, edu-juv is ranked second, and music is ranked
# third.
# If you do not include locations in the list below, they will be sorted
# alphabetically after the locations that are listed. The location is the
# location code. #
1=main
2=edu-juv
3=music

17. Location Sort Order – 949 p (Voyager 9)

18. New Voyager Location Changes
Adding new location codes to Voyager
Means possible adding to:
[LocationCodesForBibInclusion]
[LocationCodesForAVA]
[LocationSortOrder]
/m1/voyager/xxxdb/vxws/ini/PrimoExp.ini
Primo areas for new location codes:
Add to Ongoing Configuration – Institution – Primo Library Code - (required) prior to loading into Primo
Facet mapping tables for location groups or collections
This next stanza is the [LocationCodesForBibInclusion] stanza.
I’m not going to get into the nitty gritty of it – but it’s important to understand the purpose of it – and from there you can determine whether or not this is something you should consider.
The [LocationCodesForBibInclusion] stanza is used to identify the records of specific locations for extraction. This may be useful for institution
that share a single Voyager database with one instance of Primo installed or institutions with a single, multi-clustered Voyager database.
Here’s my little story about this…
I had 2 customers who were in a shared Voyager database. This database was very large and contained every state university (and I should mention they were set up as a single owning library . But only two of the libraries in the database purchased Primo. Before this [LocationCodesForBibInclusion] option was available, we needed to extract all records from the Voyager database and then use the Primo normalization rules to try and sort out the different sites – which is what we did for the situation I just mentioned. Should this new option be available then, we would have only extracted the data from the 2 libraries – based on their location codes.
This stanza just needs a list of MFHD location codes whose attached bibliographic records should be extracted for Primo.
This is based on the 852‡b of any attached MFHDs.
And please, if you rte considering using this option, you should check with your Project Manager to be sure.

19. [Institution Id] Stanza
Specify your institution
Included as a subfield in the Availability tag of records prepared for the Primo database
Used by Primo to determine ownership of the records
Voyager institution ID is set one time at system installation
Verify this setting to insure accuracy.
Institution ID = Voyager xxxdb
Let’s talk about an easier stanza now – The [Institution Id] stanza
The [Institution Id] stanza is used to specify your institution.
Really, the Institution ID equals your Voyager xxxdb
The institution ID is included as a subfield in the Availability tag of extracted records.
It’s used by Primo to essentially determine ownership of the records.
The Voyager institution ID is set by the installation team and you shouldn’t have to adjust it.
I just remind everyone to double-check the setting.

20. [Location to Primo] Stanza
Used to maintain consistency within Primo for item location codes
May be used to provide consistency in naming item location codes
Can be used to collapse locations or split locations for display in Primo
Enter the Voyager item location code first and the Primo equivalent using the format below (with each Voyager/Primo item location code entry on a separate line in the configuration file)
[Voyager Location Name]=[Primo Location Name]
Music Reserve=Reserve
Science Reserve=Reserve
NOTE: Locations not listed pass to Primo unchanged
By default, there are no locations included in the original .ini file
The next stanza is the [Location to Primo] stanza
This [Location to Primo] stanza is used to maintain consistency within Primo for item location codes.
The [Location to Primo] stanza was intended to be used by libraries to collapse locations or split locations for display in Primo.
Here’s an example of how this feature can be used
Let’s say you have 2 different Reserve locations in your catalog – Music and Science – and have decided you want them to both mapped to one location simple called Reserves
Music Reserve=Reserve
Science Reserve=Reserve
To do this, you would enter the Voyager item location code first and then the Primo equivalent using this format
[Voyager Location Name]=[Primo Location Name]
Similar to other mappings in the INI file, each Voyager to Primo item location code entry needs to be on a separate line
Please NOTE that Locations that are not listed in the [Location to Primo] stanza pass to Primo unchanged.
And By default, there are no locations included in the original .ini file.
So here’s my 2 cents on this option…
I don’t use this at all for my sites that I implement
Why would you want your Voyager data and Primo data appear different?
I always set up the Voyager locations in Primo the same way you have them set up in Voyager.
You can always manipulate the data in Primo later.

21. [Enrichment Tags] Stanza
Specify tags used to include availability, author enrichment, subject enrichment, course reserves, Rosetta and e-item information in the extract
Default Tags:
If your institution currently uses MARC 949 (or others) for another purposes you can specify an unused 9XX number for the InsertAVATag in this stanza
NOTE: Changing any default tag requires related changes (next slide)
Tag Name
Tag Field
Details
InsertAVATag
949
AVA tag contains the availability information
InsertAUTTag
950
AUT tag contains name cross-reference information
InsertSUBTag
951
SUB tag contains subject cross-reference information
InsertCRTag
952
CR tag contains course reserve information
InsertDPSTag
953
DPS tag contains Digital Preservation System (Product Rosetta) information
InsertEITMTag
954
EITM tag contains E-Item availability data (New for 8.0.0)
This next stanza -- The [Enrichment Tags] stanza is a very important stanza.
The [Enrichment Tags] stanza is used to specify the tags used to include the availability, author enrichment, subject enrichment, and course reserves data from Voyager – as well as some information from Rosetta as well.
By default, the configuration file makes the field assignments listed in the chart below.
So let’s discuss what’s included in the chart
First we have the InsertAVATag – which is added to the 949
The AVA tag contains the availability information – this is kind of the most important of the tags – and in the next slide we’ll look at everything that’s included in this tag.
The InsertAUTTag is added into the 950 and the AUT tag contains name cross-reference information
Similar to the AUT tag , we have the InsertSUBTag
The SUB tag contains subject cross-reference information and is usually added to the 951 field
Next is the InsertCRTag in the 952. The CR tag contains course reserve information
And for those of you that have Rosetta, there’s the InsertDPSTag in the 953.
The DPS tag contains Digital Preservation System (Product Rosetta) information
And finally, New to the INI file starting in 8.0, we have the InsertEITMTag.
The EITM tag contains E-Item availability data and is by default set to be in the 954.
OK – for those of you who might be panicking that we are affecting Voyager data in your database, we are not.
Think of the extract for Primo like MARC export.
We are not writing to the 949 field in Voyager, but rather the 949 field in the extracted data (which again, is in XML format).
Your Voyager data remains intact in Voyager.
All good?
So I said that these fields are the default fields that the extract uses.
But what if your library currently uses MARC 949 for another purpose – if so, you must specify a different, unused 9XX number for the InsertAVATag in the [Enrichment Tags] stanza.
The same logic applies to the other Enrichment Tags.
NOTE: Changing the default requires a matching change in the Primo configuration for harvesting – essentially you need to adjust your normalization rules.
For those of you that do know your Voyager data, or have cataloging practices set that define which 9XX fields your site uses, that’s great!
If you don’t what 9XX fields may or may not be used in Voyager, I believe there’s a script on EL Commons, or else you can probably write a query in Access to determine what fields are used or available. You may want to also ask Voyager Support if you need assistance analyzing your Voyager data.

22. [Enrichment Tags] Related Changes
Changing Default or 960 requires related changes to:
Voyager
tag range to match in: /m1/voyager/xxxdb/vxws/ini/PrimoExp.ini
960 in /m1/voyager/xxxdb/vxws/context/vxws/vxws.properties
Primo
Normalization rules for:
Display availlibrary
Links backlink
Facets for collection, toplevel and library
Search for author, subject, scope
Delivery and Institution for institution
Browse – call number
This next stanza -- The [Enrichment Tags] stanza is a very important stanza.
The [Enrichment Tags] stanza is used to specify the tags used to include the availability, author enrichment, subject enrichment, and course reserves data from Voyager – as well as some information from Rosetta as well.
By default, the configuration file makes the field assignments listed in the chart below.
So let’s discuss what’s included in the chart
First we have the InsertAVATag – which is added to the 949
The AVA tag contains the availability information – this is kind of the most important of the tags – and in the next slide we’ll look at everything that’s included in this tag.
The InsertAUTTag is added into the 950 and the AUT tag contains name cross-reference information
Similar to the AUT tag , we have the InsertSUBTag
The SUB tag contains subject cross-reference information and is usually added to the 951 field
Next is the InsertCRTag in the 952. The CR tag contains course reserve information
And for those of you that have Rosetta, there’s the InsertDPSTag in the 953.
The DPS tag contains Digital Preservation System (Product Rosetta) information
And finally, New to the INI file starting in 8.0, we have the InsertEITMTag.
The EITM tag contains E-Item availability data and is by default set to be in the 954.
OK – for those of you who might be panicking that we are affecting Voyager data in your database, we are not.
Think of the extract for Primo like MARC export.
We are not writing to the 949 field in Voyager, but rather the 949 field in the extracted data (which again, is in XML format).
Your Voyager data remains intact in Voyager.
All good?
So I said that these fields are the default fields that the extract uses.
But what if your library currently uses MARC 949 for another purpose – if so, you must specify a different, unused 9XX number for the InsertAVATag in the [Enrichment Tags] stanza.
The same logic applies to the other Enrichment Tags.
NOTE: Changing the default requires a matching change in the Primo configuration for harvesting – essentially you need to adjust your normalization rules.
For those of you that do know your Voyager data, or have cataloging practices set that define which 9XX fields your site uses, that’s great!
If you don’t what 9XX fields may or may not be used in Voyager, I believe there’s a script on EL Commons, or else you can probably write a query in Access to determine what fields are used or available. You may want to also ask Voyager Support if you need assistance analyzing your Voyager data.

23. Availability Tag (949 Field)
Contents of [Institution ID] stanza of export.ini [xxxdb] $b
Voyager Owning Library Display Name $c
OPAC Display Name of the MFHD Location $d
Call Number $e
Availability status $f
Number of items $g
Number of unavailable items $h
Multi-volume (y/n) – based on enumeration $i
Number of historical loans $j
MFHD Location Code (or temp location info) $k
Call Number indicator $p
Location Sort Order $t
Availability status text
So on the last slide I spoke about the availability information or the AVA tag.
Again, this is usually added to the 949 field or whatever field you designate in the [Enrichment Tags] Stanza.
Since this is such an important tag and contains a lot of information, I thought it was important to map it out for you…
The $a includes the Contents of [Institution ID] stanza – that we previously discussed, which is your xxxdb
The $b includes your Voyager Owning Library Display Name – whatever you have listed in SysAdmin
The $c is the OPAC Display Name of the MFHD Location
The $d contains the Call Number from the MFHD
The $e is the Availability status
The $f is the Number of items
The $g is the Number of unavailable items
The $h is to note if the record is Multi-volume (so yes or no) – The information is based on enumeration
The $i lists the Number of historical loans
And finally the $j which is the MFHD Location Code
The subfields above that are used most frequently in your normalization rules are going to be the subfield a and subfield j.

24. 952 Course Reserve
Voyager publishes bib records in XML format, which are enriched with some special fields. These fields are created in order to display holdings information and course reserves information in Primo. The fields are listed here; I won’t get into details about each of them, but they are available in the Voyager online help, as well as in the Voyager-Primo Integration Guide.

25. 954 – e Item
Voyager publishes bib records in XML format, which are enriched with some special fields. These fields are created in order to display holdings information and course reserves information in Primo. The fields are listed here; I won’t get into details about each of them, but they are available in the Voyager online help, as well as in the Voyager-Primo Integration Guide.

26. [InsertPrimoBrowseTags] Stanza
Creates Authority “Browse” search values
with cross references - see, see also, notes
If used, does not create 950 and 951 tags
Default is N
Note: There is a 2nd copy of the stanza at the bottom of the *.ini that must be deleted.
#Inserted by voy821 patch
# InsertPrimoBrowseTags, if set to Y, will include see references for
# subjects and authors that will allow Primo to construct browse searches
# from them. When InsertPrimoBrowseTags is Y, then the InsertAUTTag and
# InsertSUBTag will not be created since Primo can enrich the keyword search
# from the included Browse tags.
InsertPrimoBrowseTags=N
Note: Please check to make sure Stanza is not in the .ini twice. It was in earlier editions of 8.2

27. [DPS] Stanza
The [DPS] stanza is used to identify the link to Rosetta information when it exists.
I’m not going to say much about the [DPS] stanza – except that it is used to identify the link to Rosetta information when it exists.

28. [PrimoExp] Stanza
Identifies database extract processing considerations such as number of records to process, where to log messages, whether to use filters, and more.
Parameters may be entered on the command line or set within the configuration file. Command line paramerters override configuration file [PrimoExp] settings.
The [PrimoExp] stanza contains the following sections:
Records to Export
Bib Range Begin and Bib Range End
Bibs From File
Changed Since
Heading Changes
Availability Filter
Log File
Database Parameters
Delete Directories and Files
Course Reserve Data
So in the past few slides we’ve reviewed the following stanzas…
Item Statuses, Excluded Happening Locations, Excluded Operator IDs, LocationCodesForBibInclusion, LocationCodesForAVA, Institution ID, Location to Primo, Enrichment Tags, DPS.
Each stanza pretty much had a very specific purpose and was limited in what it did.
This next stanza, the PrimoExp stanza, is kind of a big one with many pieces and functions – but don’t panic -- like the prior stanzas, I have broken it down into digestible sections.
To be broad about The [PrimoExp] stanza, it’s used to identify database extract processing considerations such as the number of records to process, where to log messages, whether to use filters, and a bunch more.
The parameters identified in the [PrimoExp] stanza may be entered on the command line or set within the configuration file. Parameters specified on the command line override any settings within the configuration file.
In this training, I am only discussing the use of the INI file itself. The documentation on the extract has the command line details if you would prefer to handle these settings in a different way. I suggest using the INI method just so you can have a saved file with your settings in it for future reference or usage.
So what are all of these sections in the [PrimoExp] stanza?
We’re going to be talking about the following options for the extract:
Records to Export
Bib Range Begin and Bib Range End
Bibs From File
Changed Since
Heading Changes
Availability Filter
Log File
Database Parameters
Delete Directories and Files
Course Reserve Data
As well as Features that are new in Voyager 8.0 and higher versions

29. [PrimoExp] Stanza: Bibs to Export Options
Bib Range
Bibs from a file
Records Changed Since Date
So let’s start with the first section of the [PrimoExp] Stanza – the Bibs to Export Options
For any of you that have done Bulk Imports or MARC exports in Voyager, the export options should make total sense.
There are 3 different ways to determine which records you want to export / extract from Voyager
First, You can use a Bib Range (like BIB ID 1 to 1000).
Please note that is used for a range of Bib IDs and not the number of bibs. So if you deleted from Voyager 100 records between the bib range of 1 to 1000, you would only get 900 bibs extracted.
Second, You can opt for Bibs from a file (where for each bib you want extracted will have the bib ID included in a file)
And finally, you can use the Records Changed Since Date option.
I think the first 2 options are pretty straight-forward
But the third option needs a bit more explaining.
There are 2 options for the changed since date option
The first is that you manually add in the date to the INI file – using the year, month, date, dot, hour, minute, second.
The second option is to use a changedsince.txt file that has that same year, month, date, dot, hour, minute, second information in it.
I prefer the second option because the file is updated every time you run the extract – so there’s no need to keep changing the time stamp in your INI file.
I actually make use of all 3 of these Bibs to Export Options during Primo implementation
The Bib Range is good for initial extracts (and I’ll demonstrate this in just a bit)
Bibs from a file is good for when we’re only loading sample data for sites to review
And finally, the Records Changed Since Date – I use this after we have done an initial full extract and we need to refresh the Voyager data
Records Changed Since Date is primarily used for ongoing daily extracts (remember, Publishing)

30. [PrimoExp] Stanza: HeadingChanges=
Use the HeadingChanges= parameter to indicate the following:
Yes (Y), find changed headings and include all records affected.
No (N), do not look for changed headings.
Set to Y when the configuration file is used to harvest records for the Primo publishing pipe
Set to N when the configuration file is used for a full selective extract or to harvest records for the Primo availability pipe
IMPORTANT: HeadingChanges parameter requires that a setting is specified for the ChangedSince parameter. HeadingChanges can only be processed if there is a ChangedSince date.
For the initial selective extracts, the HeadingChanges= yes or no parameter does not really come into play since records have not changed when doing initial extracts.
For subsequent extracts, you would use this option.
Basically all this is for is to find changed headings and include those records that have changed in the extract.
The HeadingChanges parameter should be set to Y when the configuration file is used to harvest records for the Primo publishing pipe.
This parameter should be set to N when the configuration file is used to harvest records for the Primo availability pipe.
Please note that the HeadingChanges option can only be processed if there is a ChangedSince date – which makes since because the system needs to look at when the records were last updated and the change happened before or after the last extract was run.

31. [PrimoExp] Stanza: AvailFilter=
Use the AvailFilter= parameter to indicate the following:
Yes (Y), extract only records whose availability has changed.
No (N), export all records.
This parameter should be set to N for the initial (full) Selective extract.
IMPORTANT: AvailFilter parameter requires that a setting is specified for the ChangedSince parameter. AvailFilter can only be processed if there is a ChangedSince date.
For the initial selective extracts, the AvailFilter should be no so all records are extracted.
# AvailFilter detemines whether to export records whose availability
# fields have not changed since the last time the job ran.
# If AvailFilter is Y, only records whose availability has changed are exported;
# if AvailFilter is N, all changed records are exported.
# -A Y|N overrides this parameter on the command line
AvailFilter=N

32. [PrimoExp] Stanza: Log Options
LogFile=
Use this parameter to set the file name for the log file.
For example: primo.export.$yyMMdd$.log
The system automatically updates the $yyMMdd$ with the date/time component of the file name.
LogFileDir=
Use this parameter to set the path for the log file.
NOTE: This is automatically set at installation.
LogLevel=
LogToStdOut=
Leave the 2 parameter settings as specified in the configuration file unless directed otherwise by Ex Libris support staff.
So next we have the Log Options section of the [PrimoExp] Stanza.
There are 4 options here – but really these should have all been set during the time of installation.
I just do a quick look over on them and make sure they are OK with the correct paths, and especially the xxxdbs in them.
The LogFile parameter is used to set the file name for the log file.
For example: primo.export.$yyMMdd$.log
The system automatically updates the $yyMMdd$ with the date/time component of the file name.
LogFileDir=
Use this parameter to set the path for the log file.
And the LogLevel= and LogToStdOut.
Leave these 2 parameter settings as specified in the configuration file unless directed otherwise by Voyager Support staff.

33. [PrimoExp] Stanza: Database & User
Use this parameter to set the Oracle database name (SID).
The default is VGER.
DatabaseHost=
Use this parameter to set the database host IP address (the same as in voyager.env).
Sometimes this can also be set as localhost.
DatabasePort=
Use this parameter to set the
database port.
UserPass=
Use this parameter to specify
the Oracle database user name
and password.
NOTE: The parameters above are all set one time at system installation and in most cases, should not be changed.
There are 4 options for Database & User.
The parameters are all set at the time of installation and we advise sites not to change them.
Database=
Use this parameter to set the Oracle database name (SID). The default for most sites is typically VGER.
DatabaseHost=
Use this parameter to set the database host IP address (the same as in voyager.env). Sometimes this is set as localhost instead.
DatabasePort=
Use this parameter to set the database port.
UserPass=
Use this parameter to specify the Oracle database user name and password.
You will also notice in the screenshot that the order is a little different from how I have it laid out on the slide. We advise to leave the order as defined in the default INI file.

34. [PrimoExp] Stanza: Delete Files
The Del*Dir and Del*File are used to determine when records are deleted from Voyager.
These standard paths and names are automatically set at installation.
Important: Extracts must be run on same server where the deleted.* files reside
So this next section of the [PrimoExp] Stanza is for the Delete Files on your Voyager server.
Basically, how would the extract know if a bib, MFHD or item was deleted in Voyager? It looks at the Delete directories and files on your Voyager server.
These standard paths and names are automatically set during your installation – but again, always check them over, especially the xxxdb.
Also in Voyager 7, the option to extract eitems was not available – but it was added in Voyager 8, so the lines for the delete eitems directory and file have been added to the INI file.
And I can’t stress enough that Extracts must be run on same server where the delete files reside.
Should you get a new Voyager server, or go through an upgrade, please inform your upgrader that you need these files intact.

35. [PrimoExp] Stanza: Course Reserves
Parameter
Description
CourseReserves=N
Set to Y to include course reserve data.
IncludeReserveListItemsSuppressedBibs=N
NEW FOR 8.1.0
Set to Y to export suppressed bibs that are linked to reserve list items.
This flag will have no effect on suppressed bibs that are not linked to reserve list items, and will be ignored if the CourseReserves flag is set to N.
So this slide focuses on how the extract handles Course Reserves & E-Item data.
Keep in mind, that for these flags, you should make use of them for your extracts even if you aren’t using Voyager course reserves data in Primo right away but if you think you might incorporate it in the future to avoid having to run full initial extracts later down the road.
So – do you want to include Course Reserve data – yes or no.
This next option is new to Voyager 8.1.0
Do you want to export suppressed bibs that are linked to reserve list items.
IncludeReserveListItemsSuppressedBibs= yes or no
This flag will have no effect on suppressed bibs that are not linked to reserve list items, and will be ignored if the CourseReserves flag is set to N.
These next 3 options were all introduced in Voyager 8.0
Do you want to ExportEItemsWithCourseReserves – yes or no?
If this flag is set to Y and the CourseReserves flag is set to N, then this flag overrides the value of the CourseReserves flag, as E-Items are linked to course reserves.
For the IncludeEItemSuppressedBibs – do you want to export suppressed bibs that are linked to E-Items – yes or no
This flag will have no effect on suppressed bibs that are not linked to E-Items, and will be ignored if the ExportEItemsWithCourseReserves flag is set to N.
And finally EItemAvailability
The EItemAvailability flag determines the availability status value for all exported E-Items.
• C (check availability) – this is the DEFAULT
• A (available)
• U (unavailable)

36. [PrimoExp] Stanza: E-Items
Parameter
Description
ExportEItemsWithCourseReserves=N
NEW FOR 8.0.0
Set to Y to include E-Item data.
If this flag is set to Y and the CourseReserves flag is set to N, then this flag overrides the value of the CourseReserves flag, as E-Items are linked to course reserves.
IncludeEItemSuppressedBibs=N
Set to Y to export suppressed bibs that are linked to E-Items.
This flag will have no effect on suppressed bibs that are not linked to E-Items, and will be ignored if the ExportEItemsWithCourseReserves flag is set to N.
EItemAvailability=C
The EItemAvailability flag determines the availability status value for all exported E-Items.
• C (check availability) -- DEFAULT
• A (available)
• U (unavailable)
So this slide focuses on how the extract handles Course Reserves & E-Item data.
Keep in mind, that for these flags, you should make use of them for your extracts even if you aren’t using Voyager course reserves data in Primo right away but if you think you might incorporate it in the future to avoid having to run full initial extracts later down the road.
So – do you want to include Course Reserve data – yes or no.
This next option is new to Voyager 8.1.0
Do you want to export suppressed bibs that are linked to reserve list items.
IncludeReserveListItemsSuppressedBibs= yes or no
This flag will have no effect on suppressed bibs that are not linked to reserve list items, and will be ignored if the CourseReserves flag is set to N.
These next 3 options were all introduced in Voyager 8.0
Do you want to ExportEItemsWithCourseReserves – yes or no?
If this flag is set to Y and the CourseReserves flag is set to N, then this flag overrides the value of the CourseReserves flag, as E-Items are linked to course reserves.
For the IncludeEItemSuppressedBibs – do you want to export suppressed bibs that are linked to E-Items – yes or no
This flag will have no effect on suppressed bibs that are not linked to E-Items, and will be ignored if the ExportEItemsWithCourseReserves flag is set to N.
And finally EItemAvailability
The EItemAvailability flag determines the availability status value for all exported E-Items.
• C (check availability) – this is the DEFAULT
• A (available)
• U (unavailable)

37. [PrimoExp] Stanza: Bundle
BundleDir=
Use this parameter to specify the directory where the bundled *.tar.gz files (see BundleFile=) are to be placed.
NOTE: This is automatically set at installation.
BundleFile=
Use this parameter to identify the naming convention for the .tar and .tar.gz files that contain the files/records being exported in groups of records determined in the [XMLWriterProtocol] stanza.
NOTE: The naming convention for the.xml files that are bundled is defined in the [XMLWriterProtocol] stanza. The bundled file names are appended with the group ID and suffix.
The last section of the [PrimoExp] Stanza is regarding bundling.
In an earlier slide, we had looked at primo-related files and directories on your Voyager server – listing the path of /m1/voyager/xxxdb/primo/Selective/bundled
That’s where this comes into play.
The BundleDir parameter specifies the directory where the bundled *.tar.gz files are to be placed. This is automatically set at installation – but again, just look at this setting and ensure that it’s populated with your db code (and not xxxdb)
The BundleFile parameter is used to identify the naming convention for the .tar and .tar.gz files that contain the files/records being exported.
We’re going to look at the [XMLWriterProtocol] stanza next – which has a little more definition it about the naming convention for the.xml files.

38. [XMLWriterProtocol] Stanza
The [XMLWriterProtocol] stanza defines the storage location of the XML records and number of records in the tar.gz file for the XML records targeted for export to the Primo database.
Parameter
Description
File=
Use this parameter to identify the file naming convention for the XML files generated from harvesting Voyager records for export to the
Primo database.
For example: primo.export.$yyMMddhhmmss$.xml
XSL=
Leave this parameter blank. No setting required.
recsPerGroup=
Use this parameter to identify the number of records you prefer to be saved in each tar.gz file.
Important: Do not include more than 10,000 records in a single .tar file. There is a 10MB maximum, file-size limit for Primo throughput.
Recommended: 1,000 to 5,000 records per file
idPrefix=
UsePrettyPrint=
Use this parameter, set to Y (Yes), for more readable XML files.
NOTE: Using the pretty print Y option risks altering data with leading and trailing spaces.
Use the N (No) option for machine-readable files when human review is not a requirement.
The N (No) option is the default.
The File parameter is used to identify the file naming convention for the XML files generated from harvesting Voyager records for export to thePrimo database.
For example: primo.export.$yyMMddhhmmss$.xml
The XSL parameter should be left blank.
The recsPerGroup is an important parameter -- you want to Use this parameter to identify the number of records you prefer to be saved in each tar.gz file.
I can't stress enough that you should not include more than 10,000 records in a single .tar file.
There is a maximum, file-size limit for Primo that is estimated to be 10,000 MARC records which is why we emphasize this limit.
The next parameter is idPrefix and this should be left blank.
And lastly, there's the UsePrettyPrint option -- which is a setting if you want more readable, or supposedly, pretty XML files.
NOTE: Using the pretty print Y option risks altering data with leading and trailing spaces.
Use the N (No) option for machine-readable files when human review is not a requirement.
The N (No) option is the default -- which is how I always leave it.
So, I know there are a lot of sections in the INI file, and now to lay 5 more sections from the XMLWriterProtocol] Stanza on you -- but really, I just you need notice 2 things on this page --
the first is the light blue section which covers the number of records you prefer to be saved in each tar.gz file. Remeber that 10,000 record limit.
And finally, the INI file's best instruction -- # EVERYTHING BELOW THIS LINE IS INTERNAL DO NOT MODIFY
That's my queue that I finished all of my options in the INI file and I can go ahead and save it.
# EVERYTHING BELOW THIS LINE IS INTERNAL DO NOT MODIFY

39. Manually Running Extracts
From selective directory:
/m1/voyager/xxxdb/sbin/Pprimoexp.sel -f ../ini/PrimoExp-Selective.ini
From sbin:
Pprimoexp.sel -f m1/voyager/xxxdb/ini/PrimoExp-Selective.ini
Selective Extract
From sbin directory:
Pprimoexp.pub -f ../ini/PrimoExp-Publishing.ini
Publishing Extract
So you’ve customized your PrimoExp-INI file to meet the needs of your Voyager data for Primo
Now it’s time to prepare for actually running the extract itself – exciting.
So for every type of extract, whether it be Selective, Publishing , or Availability, you have an extract-type specific INI file.
And in the SBIN directory, you should have a corresponding extract-type specific script
For the Selective extract and INI, you’ll have the Pprimoexp.sel script
For Publishing, it’s Pprimoexp.pub
And for Availability, the Pprimoexp.avail script
Let’s look at the Selective extract example here
The command line basically consists of the script and the path to & name of the INI file
So Pprimoexp.sel (which is the script) and -f m1/voyager/xxxdb/ini/PrimoExp-Selective.ini (which is the path and name)
And you can always skip mapping out the full /m1/voyager/xxxdb/ portion of the path too by using Pprimoexp.sel -f ../ini/PrimoExp-Selective.ini

40. Extra Logging for Selective Extract
One log daily: /m1/voyager/xxxdb/primo/Selective/logs
Create multiples using nohup.out for each selective extract
nohup.out Pprimoexp.sel -f m1/voyager/xxxdb/ini/PrimoExp-Selective.ini &
A nohup.out log file will then be created in the /sbin directory
Rename your nohup.out file with, for example, the end of your range (if not renamed, it appends) to keep a record of each selective extract
nohup.out (1-10,000)
nohup.out (10,001-20,000)
Then move your nohup.out file to the Selective log file directory: /m1/voyager/xxxdb/primo/Selective/logs
NOTE: For future extracts (i.e. Publishing or Availability) you should review the
Extract Log Summary section in the Voyager® Primo® Integration User’s Guide.
Since the log file created in /m1/voyager/xxxdb/primo/Selective/logs appends all of your extracts into one daily file, it helps to keep separate logs for each extract (especially when using the range of bib ids)
You just need to add the nohup.out to the begging of your command line and an amersand at the end of it --
so it looks like the following: nohup.out Pprimoexp.sel -f m1/voyager/xxxdb/ini/PrimoExp-Selective.ini &
Doing this will create a nohup.out log file will in the /sbin directory
At the completion of each extract, just rename your nohup.out file with, for example, the end of your range.
So nohup.out (1-10,000)
And nohup.out (10,001-20,000)
Keep in mind that if the nohup.out file is not renamed, it appends
Then just move your nohup.out file to the Selective log file directory: /m1/voyager/xxxdb/primo/Selective/logs where your daily log file lives
I'll show this extra logging and file moving in action during the demo -- which is coming right up.
It's important to NOTE that For future extracts (i.e. Publishing or Availability) you should review the Extract Log Summary section in the Voyager® Primo® Integration User’s Guide.

41. Review Are the extract pieces on the Voyager server?
/m1/voyager/xxxdb/primo for directories
Selective, Publishing, Availability
exports, bundled, logs
/m1/voyager/xxxdb/sbin -- Pprimoexp.* (scripts)
/m1/voyager/xxxdb/ini -- PrimoExp-*.ini (initialization files)
What kind of extract do you want to do?
Have you filled out the PrimoExp-*.ini correctly?
Where will your log files be?
Should you consider extra logs? (nohup.out)
We’ve already covered a lot so far – and I just want to do a simple brief review before I conduct the live demo for you.
This actually serves more like a check list for you when you’re ready to do an extract – and most of it is actually is useful to verify if the needed Voyager-Primo integration pieces are present on your Voyager server.
First thing -- Are the extract pieces on the Voyager server?
Go and check in your /m1/voyager/xxxdb/primo directory for the Selective, Publishing, & Availability directories
In each of those, are the exports, bundled, and logs directories present?
Now, you’ll want to check the /m1/voyager/xxxdb/sbin directory and look for the 3 Pprimoexp scripts
And of course, look in /m1/voyager/xxxdb/ini and verify that the 3 INI files are present, the PrimoExp.ini or initialization files
So, What kind of extract do you want to do?
Have you filled out your PrimoExp.INI file with all of your needed options?
Where will your log files be?
And finally, should you consider extra logging? Like using the nohup.out trick.

42. Voyager Selective Extract
Demonstration
Voyager Selective Extract
For the demo:
Go through the selective.ini on the server
Do an extract for records with a bib range of 1 to 1000
Add the nohup.out to the command line
Do a tail –f on the nohup.out file so they can see the extract in process
Show the nohup.out file in the sbin
Move it to the /logs directory
Show them the daily log
Ask if there are any questions

43. Automating Extracts via Cron Jobs
On Voyager server, type “crontab –e” (in edit mode)
Sample from crontab:
00 01 * * * /m1/voyager/xxxdb/sbin/Pprimoexp.pub
-f /m1/voyager/xxxdb/ini/PrimoExp-Publishing.ini
00 01 is the time to run daily – so the cron above will run at 00:01 am every day
OK everyone – we’re almost there – just 4 more slides to go.
Let’s say that you’ve completed all of your initial extracts and are ready to set up your daily extracts – or Publishing extracts.
You don’t really want to have to manually run the job every day – so why not cron the job instead?
On Voyager server, type “crontab –e” – this puts the crontab in the edit mode
Here’s a sample sample from crontab:
00 01 * * * /m1/voyager/xxxdb/sbin/Pprimoexp.pub -f /m1/voyager/xxxdb/ini/PrimoExp-Publishing.ini
01 is the time to run daily – so the cron above will run at 01:00am every day
It’s a publishing script using the publishing INI.
And then this cron updates the ChangedSince.txt file for future extracts.
One thing I will note here is that Voyager Support has suggested to not include the “touch” and that if an extract runs successfully it should update the ChangedSince.txt file on its own.
PLEASE REMOVE the Touch command from Cron Tab entries as you find them. For Primo Extracts.

44. Excluded Records
When identifying bibliographic records for the initial data load, the following criteria is used to identify records to be excluded
If a bibliographic record is suppressed from the OPAC
If a bibliographic record was most recently modified at one of the excluded happening locations as identified in the configuration file
If a bibliographic record was most recently modified by one of the excluded operators as identified in the configuration file
Other available record exclusion factors in Voyager 8
NOTE: After the initial/Selective extracts, the Extract Log Summary section in the Voyager® Primo® Integration User’s Guide discusses additional logging, including discussion of reasons why records were not extracted.
I also would like to mention that after your initial/Selective extracts, the Voyager® Primo® Integration User’s Guide has a section on the Extract Log Summary and discusses additional logging, including more reasons why records were not extracted.

45. What was added for Voyager 8?
This will allow the inclusion of e-item records in the records extracted for course reserve materials.
Exporting e-items for Primo
By providing a list of MFHD location codes, one can specify which bibs should be extracted, based on the 852 $b of any attached MFHDs.
Extracting records for specific locations
Exported records will be written to a tar file rather than writing each record to a file and bundling the records in tar files in a separate process. In addition, a new option has been added to the Voyager extract process to split a range of bib IDs into multiple processes so that the extract will run in less time.
Performance improvements in the Voyager extract
The extract log includes the bib ID of the records skipped during the extract, along with the reason each record was skipped, the total number of records extracted during the process, and the amount of time the extract took.
Enhanced logging
For those of you who are still on Voyager 7, it is important to note the enhancements that have been added into the Voyager extract for Primo – either in Voyager 8.0 or 8.1.
We’ve discussed these while looking through the various sections of the PrimoExp INI – but it’s still good to know what’s new and nifty in newer Voyager releases
Not on the list is the 8.2 extract of additional authority information for Browse. BTW, I’ve just had my first introduction to Voyager 9. If you are still on Voyager 7, it is time to upgrade!

46. Other Resources Voyager Support Team
Voyager -Primo Integration User Guides
Ex Libris Documentation Center  Integrations  Technical Documentation  Voyager-Primo
Voyager Release Notes
Ex Libris Documentation Center  Voyager  Upgrade Release Planning  Version #
Defect Fixes and/or Enhancements
eService (for Cases, Issues)
If opening a case, make sure to select Voyager as your product.
KnowledgeBase available for known issues
Voyager Support Team
Well, we’ve pretty much come to the end of today’s training – and although we covered a lot today – I don’t want this to be the only reference that you have regarding the Voyager extract for Primo.
There are several other resources available to you about the extract.
The first resource is the Voyager-Primo Integration User Guides available in the Documentation Center.
I’m going to warn you now – you will not find this documentation in either the Voyager or Primo folders.
You will need to go to the Integrations folder and in Technical documentation, you will see a section for Voyager-Primo.
That’s where the various versions of the Voyager-Primo Integration User Guides live – and they should have the Voyager release version noted in the name.
The second resource you can refer to are the Voyager release notes.
These are great for checking on various Defect Fixes and/or Enhancements in the Voyager extract. You’ll may want to consider checking the release notes for your current version, as well as future versions.
The Voyager release notes are also on the Documentation Center – but you will want to got the Voyager section and look in the Upgrade Release planning folder.
The third resource is going to be eService.
So if you have not noticed a trend in the resources as of yet – here it is – it’s all about Voyager.
The Voyager extract for Primo is just another Voyager program in the sbin directory – it’s an extract on the Voyager server, developed and supported by the various Voyager Teams – and not Primo teams.
Now once the data is imported into Primo, that’s when the Primo team jumps in. But when it comes to running the extract itself and any problems or questions that you have – the Voyager Support team will be your best resource. And that’s why I list the Voyager Support Team as a resource for the Voyager extract for Primo.
And that’s all I have for you today.
Are there any questions?
Hearing no other questions – I want to thank everyone for attending the Voyager extract for Primo training.

47. Resources (Salesforce Articles)
Salesforce Articles relevant to Voyager Extract:
KCS How to check Primo extract logs on Voyager server?
KCS 4566 Primo Extract is taking a long time after loading a large authority file
KCS Implement Location Sort Order for VPRIMO
KCS Can extract all records in one process?
KCS How to enable Primo Browse tags in Voyager?