Problem Symptoms

Existing Voyager holdings records that have 855/865 pairs do not display this data in Primo or in the vxws services.

Cause

If the 855/865 pair has an indicator that is not included in the Valid865Indicators_1 and Valid865Indicators_2 values in the /m1/voyager/yyydb/tomcat/vxws/context/vxws/xsl/configs/104X_config.xml file, the 855/865 pair will not be included in the vxws services and subsequently won't display in Primo

Resolution

1. Note which indicators are selected in the 855/865 pairs in the holdings record in Voyager
2. Edit the /m1/voyager/yyydb/tomcat/vxws/context/vxws/xsl/configs/104X_config.xml file
3. Look for these lines:

<!--    Pairs of 855/865 fields will not be displayed unless the 1st indicator is 
                        listed below.-->
                        <Valid865Indicators_1>4</Valid865Indicators_1>

<!--    Pairs of 855/865 fields will not be displayed unless the 2nd indicator is 
                        listed below.-->
                        <Valid865Indicators_2>1</Valid865Indicators_2>

4. Make sure that any first and second indicator in step 1 above is included in the values for Valid865Indicators_1 and Valid865Indicators_2 (separated by a comma) -- for example, if the 855/866 pair in step one has a first indicator of 2 and a second indicator of 0, edit the lines from step 3 to look like this:

<!--    Pairs of 855/865 fields will not be displayed unless the 1st indicator is 
                        listed below.-->
                        <Valid865Indicators_1>2,4</Valid865Indicators_1>

<!--    Pairs of 855/865 fields will not be displayed unless the 2nd indicator is 
                        listed below.-->
                        <Valid865Indicators_2>0,1</Valid865Indicators_2>

After this change, 855/865 pairs will show in the vxws service as an 868 field, and will display in Primo (if properly configured in Primo).

Additional Information

For additional configuration steps on the Primo side, please see the Configuring the Display of Holdings Records section in the Primo Interoperability Guide.

• Article last edited: 06-May-2021