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

    WEB: Voyager doesn't return all holdings for Record Holdings service requests

    • Article Type: Known Issue
    • Product: Voyager
    • Product Version: 8.0.0
    • Relevant for Installation Type: Dedicated-Direct; Direct; Local; Total Care

    Symptoms

    * Holdings data for some locations is displayed in WebVoyage, but not in Primo
    * Primo's Availability tab displays message: "There are no items to display for this location."
    * Item status in Primo still listed as Available or Unavailable, despite holding not displaying
    * Requests made to vxws using Record Holdings API service do not return all holdings
    * Holdings location is not part of a circulation policy definition

    Defect Status

    Issue 16384-17761/VYG-1422 is resolved for Voyager 8.2.1 and higher.

    Replication Steps

    1. Find a bib record with multiple mfhds, one of which is not in a circ policy definition.
    2. Use Record Holdings service to make a request:
    http://[server]:[port]/vxws/record/[bibID]/holdings?view=Full
    3. Note that holdings information for the location not in a circ policy definition is not returned in the XML from Voyager.
    4. Add the location to a circulation policy definition in SysAdmin.
    5. Make request again. Note that holdings information for that location is now returned by Voyager.

    Workaround

    Add location to a circ policy in SysAdmin > Circulation > Policy Definitions > Locations tab

    Additional Information

    WebVoyage will display the holdings data regardless of whether or not the location is in a circulation policy definition.

    Category: Circulation


    • Article last edited: 10/8/2013
    //doorbell.io feedback widged