Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    vxws: confusing error message when call slip fails

    • Product: Voyager
    • Product Version: 8.1.1


    When PDS formats group_id as group-id when submitting a Call Slip request via RESTful API, Voyager returns “Item is on order” rather than an error message indicating there is a problem with the API request.

    Defect Status

    Issue 16384-20305 / VYG-4595 is currently in Development.

    Replication Steps

    1. In Primo <institution>_primo.tags file, set v-group-id=group-id
    2. Identify a test patron and item, and in Voyager SysAdmin, ensure that Call Slip is allowed in the policy matrix.
    3. Submit a call slip request via Primo interface, or by manually submitting PUT request:


    <?xml version="1.0" encoding="UTF-8"?>
    <comment>testing callslip request</comment>
    <reqinput field="1">Volume</reqinput>
    <reqinput field="2">Issue</reqinput>
    <reqinput field="3">Year</reqinput>

    XML response:

    <reply-text>Failed to create request</reply-text>
    <note type="error">The item is on order.</note>
    1. Note type field is what displays in Primo.
    2. Now either trim the patron_group parameter from the URL, or set <institution>_primo.tags file, v-group-id=group_id
    3. (underscore instead of hyphen in group_id)
    4. Resubmit same request. XML response:
    <note type="">Your request was successful.</note>


    Ensure <institution>_primo.tags file has v-group-id=group_id

    • Article last edited: 16-Mar-2015
    • Was this article helpful?