Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Voyager

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Voyager
    3. Knowledge Articles
    4. "Library Has" holdings fields display twice in Tomcat

    "Library Has" holdings fields display twice in Tomcat

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Additional Information
    • Article Type: General
    • Product: Voyager
    • Product Version: 7.2.2

    Problem Symptoms:

    • "Library Has" holdings fields display twice in Tomcat OPAC.
    • MARC 866 fields are not duplicated in holdings records in Cataloging.


    Cause:
    File displayHoldings.xml has redundant specifications for 866 field display.

    Resolution:
    Edit /m1/voyager/xxxdb/tomcat/vwebv/context/vwebv/ui/[skin]/xsl/contentLayout/configs/displayHoldings.xml to remove redundant specifications for MARC 866 display.

    *See the "See Also" section at the bottom of this article.

    Additional Information

     

    Example 1a: OPAC display with redundant "Library Has" display data:

    Number of items: 150
    Status: Not Charged
    Library Has: v.1-160 (1988-2011)
    v.1-160 (1988-2011)


    Example 1b: displayHoldings.xml containing redundant display data.

    Note: in the example below, the top 866 line "<displayTag field="866" indicator1="|" indicator2="|" subfield="az" />" is redundant with subsequent ones with spelled-out indicators causing a duplicate display of the "Library Has" data.


    <holdingsTags label="Current Issues:">
    <displayTag field="866" indicator1="|" indicator2="|" subfield="az" /> << displays 866 fields
    <displayTag field="1020" />
    </holdingsTags>

    <holdingsTags label="Library Has:">
    <displayTag field="1040" />

    <displayTag field="866" indicator1="|" indicator2="0" subfield="az" /> << redundant with top displayTag line
    <displayTag field="866" indicator1="|" indicator2="1" subfield="az" /> << redundant with top displayTag line
    <displayTag field="866" indicator1="|" indicator2="2" subfield="az" /> << redundant with top displayTag top line
    <displayTag field="866" indicator1="3" indicator2="0" subfield="az" /> << redundant with top displayTag top line
    <displayTag field="866" indicator1="3" indicator2="1" subfield="az" /> << redundant with displayTag line
    <displayTag field="866" indicator1="3" indicator2="2" subfield="az" /> << redundant with top displayTag line
    <displayTag field="866" indicator1="4" indicator2="0" subfield="az" /> << redundant with top displayTag line
    <displayTag field="866" indicator1="4" indicator2="1" subfield="az" /> << redundant with top displayTag line
    <displayTag field="866" indicator1="4" indicator2="2" subfield="az" /> << redundant with top displayTag line
    <displayTag field="866" indicator1="5" indicator2="0" subfield="az" /> << redundant with top displayTag line
    <displayTag field="866" indicator1="5" indicator2="1" subfield="az" /> << redundant with top displayTag line
    <displayTag field="866" indicator1="5" indicator2="2" subfield="az" /> << redundant with top displayTag line
    <displayTag field="899" indicator1="X" indicator2="X" subfield="a" /> << redundant with top displayTag line
    </holdingsTags>

    Example 2a: OPAC display without redundant "Library Has" display data:
    Number of items: 150
    Status: Not Charged
    Library Has: v.1-160 (1988-2011)

    Example 2b: displayHoldings.xml with redundancy commented out:

    <holdingsTags label="Current Issues:">
    <displayTag field="866" indicator1="|" indicator2="|" subfield="az" />
    <displayTag field="1020" />
    </holdingsTags>

    <holdingsTags label="Library Has:">
    <displayTag field="1040" />
    <!--
    <displayTag field="866" indicator1="|" indicator2="0" subfield="az" />
    <displayTag field="866" indicator1="|" indicator2="1" subfield="az" />
    <displayTag field="866" indicator1="|" indicator2="2" subfield="az" />
    <displayTag field="866" indicator1="3" indicator2="0" subfield="az" />
    <displayTag field="866" indicator1="3" indicator2="1" subfield="az" />
    <displayTag field="866" indicator1="3" indicator2="2" subfield="az" />
    <displayTag field="866" indicator1="4" indicator2="0" subfield="az" />
    <displayTag field="866" indicator1="4" indicator2="1" subfield="az" />
    <displayTag field="866" indicator1="4" indicator2="2" subfield="az" />
    <displayTag field="866" indicator1="5" indicator2="0" subfield="az" />
    <displayTag field="866" indicator1="5" indicator2="1" subfield="az" />
    <displayTag field="866" indicator1="5" indicator2="2" subfield="az" />
    <displayTag field="899" indicator1="X" indicator2="X" subfield="a" />
    -->
    </holdingsTags>

    See also:

    Recent Issues display twice and include the journal title in Voyager WebVoyage

    Webvoyage Architecture Overview and Configuration Models and KB item 16384-57682.

    Category: Opac


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • "INVALID RECORD DATA! It must contain Patron Group 1!Record written to exception file"
      • "Location code not selected. Location ID defaults to 0" when run catjob 13
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Voyager
    2. Tags
      This page has no tags.
    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