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

    extract:if deletes contain 001 w/spaces, extract dies

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Voyager
    • Product Version: 8.1.2

    Description:
    Bug Report Form for Issue 16384-18049

    Module(s): Voyager/Primo extract
    Server platform(s) affected: Solaris/all
    PC OS (if applicable): n/a
    Browser & version (if applicable): n/a
    Release(s): reported in 7.2.1, replicated in 8.1.0

    Expected results: Extract should log error but continue if it encounters unexpected data in the deleted.bib.marc file.

    Actual results: If the extract hits a deleted record that has an 001 padded with spaces, the extract dies without processing the rest of the deleted.bib.marc file.

    Workflow implications: Deleted records aren’t being removed from Primo

    Replication steps:
    Run a Publishing extract (which will check for deleted.bib.marc and process it) on a deleted.bib.marc file that contains at least one deleted record that has an 001 padded with spaces after the bib_id.
    Check the log file – you’ll see an error like this:

    2012-03-23 05:20:51,814 349547 [main] FATAL com.endinfosys.voyager.primo.PrimoExp - Caught exception
    java.lang.NumberFormatException: For input string: "225361 "

    You’ll also note that the deleted.bib.marc file was not renamed with a time/date stamp.

    Other information: If you remove the extraneous spaces from the 001 in each problem record in the deleted.bib.marc, it will process successfully.

    Workaround: Marc export all affected records and then run a bulk import matching on bib_id to overlay all the affected records.

    Resolution:
    Fixed in Voyager 8.1.2.

    • Article last edited: 3/18/2015