Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Primo extract creates empty AVA tag when no holdings for bib

    • Article Type: General
    • Product: Primo
    • Product Version: 9

    Problem Symptoms:
    * Bib with no holdings records, or all holdings Suppressed from OPAC extracted with AVA tags with empty subfield code tags
    * Resulting <availlibrary> tag presents misleading location/holdings in calculated availability statement in Primo

    Cause:
    This behavior is the result of Issue VYG-6151.

    Resolution:
    VYG-6151 is currently in Development.

    Additional Information

    Replication steps:
    1. In Cataloging, identify a bib record with no holdings (either no attached mfhds, or all mfhds suppressed from OPAC)
    2. Use Primo Extract to extract record.
    3. Inspect resulting XML and note 949:
    <datafield ind2=" " ind1=" " tag="949">
    <subfield code="a">xxxdb</subfield>
    <subfield code="b"/>
    <subfield code="c"/>
    <subfield code="d"/>
    <subfield code="e">check_holdings</subfield>
    <subfield code="f">0</subfield>
    <subfield code="g">0</subfield>
    <subfield code="h">N</subfield>
    <subfield code="i">0</subfield>
    <subfield code="j"/>
    <subfield code="k"/>
    </datafield>

    4. AVA tag is created without any significant data. When Primo processes this XML into PNX, it generates availlibrary entry for this "location":
    <availlibrary>$$IPRIMO$$L$$1$$2( )$$Scheck_holdings$$30$$40$$5N$$60$$Xxxxdb$$Y$$O{prefix}{bib_id}</availlibrary>
    5. If deduped with another record with a holdings location, shows "Available at {holdings location from other record} and other locations" and Location tab shows only {holdings location from other record}.

    Category: Interoperability (Voy) - Voyager

    Subject: Primo (Voy) - Voyager


    • Article last edited: 9/18/2014
    //doorbell.io feedback widged