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

    Pipe fail with errors: Invalid content was found starting with element 'XXX'. One of '{YYY}' is expected

    • Product: Primo
    • Product Version: All
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local

     

    Problem Symptoms


    Primo Pipe fails with the following errors:  
    Invalid content was found starting with element 'XXX'. One of '{YYY}' is expected  

    Errors for examples:
    •    Invalid content was found starting with element 'XXX'. One of '{title}' is expected
    •    Invalid content was found starting with element 'XXX'. One of '{type}' is expected
    •    Invalid content was found starting with element 'XXX'. One of '{ sourcerecordid}' is expected
    •    Invalid content was found starting with element 'XXX'. One of '{delivery}' is expected.

     

    Cause


    In Primo PNX record there are several mandatory fields. When one of them can't be created, the record will fail with this error. If many records failed with this error and the pipe threshold was exceeded - the pipe will fail.

    The mandatory fields are: 
    •    Controltype – sourcerecordid, sourceid and recordid
    •    Displaytype – type and title
    •    Deliverytype – delcategory

     

    Resolution


    •    Check the Normalization Rules with the failing record metadata and see what seems to be the problem.
    •    Check if more than one mandatory fields are being created, for example two display/type. This will also cause the Pipe to fail as only one is allowed.

     

    Additional Information


    There are more errors with the same error structure such as:
    “Invalid content was found starting with element 'ranking'. One of '{browse}' is expected.”
    Invalid content was found starting with element 'recordid'. One of '{sourcedbandrecordid, originalsourceid, ilsapiid, recordtype, addsrcrecordid, sourcetype, sourceformat, sourcesystem, lastmodified, almaid, colldiscovery}' is expected.
    These are indicating different issues usually pointing to a discrepancies between the normalization rules and the source.

     


    • Article last edited: 05-Oct-2016
    //doorbell.io feedback widged