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

    vxws:missing ISBN and ISSN in web service "SearchService"

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

    Description:
    Issue number: 16384-19073
    Module: vxws
    Server platform affected: Solaris

    Releases replicated in: 8.1.1-8.1.2
    Last version without bug: 8.1.0

    Expected results:
    SearchService should include ISBN and ISSN in results.

    Actual results:
    ISBN and ISSN are returned as <sear:isbn xsi:nil="true"/> and <sear:issn xsi:nil="true"/> for all records, no matter if the ISBN and ISSN are in the records or not.

    Workflow implications: Anything that uses this service to pull the ISBN or ISSN does not work correctly.

    Replication steps:
    From this example URL: http://10.100.3.44:10014/vxws/SearchService?searchCode=CALL&searchArg=PS21&browseFlag=Y

    Record that has an ISBN present though it does not display:
    <sear:result>
    <sear:bibId>39253</sear:bibId>
    <sear:bibText1>Magill's survey of American literature / edited by Frank N. Magill.</sear:bibText1>
    <sear:bibText2 />
    <sear:bibText3>1991</sear:bibText3>
    <sear:callNumber>PS21 .M34 1991</sear:callNumber>
    <sear:mfhdCount xsi:nil="true" />
    <sear:itemCount xsi:nil="true" />
    <sear:itemStatusCode xsi:nil="true" />
    <sear:patronGroupCode xsi:nil="true" />
    <sear:locationName xsi:nil="true" />
    <sear:opacSuppressFlag xsi:nil="true" />
    <sear:relevanceRanking xsi:nil="true" />
    <sear:headingText xsi:nil="true" />
    <sear:headingType>Library of Congress</sear:headingType>
    <sear:indexCode>U</sear:indexCode>
    <sear:databaseCode xsi:nil="true" />
    <sear:elink xsi:nil="true" />
    <sear:elinkType xsi:nil="true" />
    <sear:isbn xsi:nil="true" />
    <sear:issn xsi:nil="true" />
    <sear:bibFormat xsi:nil="true" />
    <sear:patronFirstName xsi:nil="true" />
    <sear:patronLastName xsi:nil="true" />
    </sear:result>

    Workaround: None

    Resolution:
    Fixed in 8.2.0.


    • Article last edited: 3/16/2015
    //doorbell.io feedback widged