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

    vxws: confusing error message when call slip fails

    • Article Type: General
    • Product: Voyager
    • Product Version: 8.1.1

    Description:
    Issue number: 16384-20305
    Module: vxws / RESTful Call Slip API
    Server platform affected: all
    PC OS: n/a
    Browser & version: n/a

    Releases replicated in: 8.1.1
    Last version without bug: n/a

    Expected results:
    When PDS formats patron information sent to Voyager in a way it cannot parse, Voyager would return an error message to that effect.

    Actual results:
    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.

    Workflow implications: Call Slip requests are submitted and not accepted by Voyager, but patrons and staff may be unable to determine why.

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

    http://<ip>:<port>/vxws/record/<bib_id>/items/<item_id>/callslip?patron=<patron_id>&patron_homedb=1@ABERDB20020722161758&patron_group=<patron_id>

    <?xml version="1.0" encoding="UTF-8"?>
    <call-slip-parameters>
    <comment>testing callslip request</comment>
    <dbkey>1@[DBKEY]</dbkey>
    <reqinput field="1">Volume</reqinput>
    <reqinput field="2">Issue</reqinput>
    <reqinput field="3">Year</reqinput>
    </call-slip-parameters>

    XML returned by that request:

    <response>
    <reply-text>Failed to create request</reply-text>
    <reply-code>25</reply-code>
    <create-call-slip>
    <note type="error">The item is on order.</note>
    </create-call-slip>
    </response>

    Note type field is what displays in Primo.

    Now either trim the patron_group parameter from the URL, or set <institution>_primo.tags file, v-group-id=group_id
    (underscore instead of hyphen in group_id)

    Submit same request. XML returned:
    <response>
    <reply-text>ok</reply-text>
    <reply-code>0</reply-code>
    <create-call-slip>
    <note type="">Your request was successful.</note>
    </create-call-slip>
    </response>

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

    Resolution:


    • Article last edited: 3/16/2015