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

    Incorrect fields from existing bib retained during merge when using bulk import

    1. Last updated
    2. Save as PDF
    • Product: Voyager
    • Product Version: all
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

     

    Symptoms

    When bulkimporting a file of bibs using a Bib Dup Detection profile set to merge, if the bulk import rule has both a Bib Dup Detection profile and an Auth Dup Detection profile selected (though the incoming file is only bibs so the Auth Dup profile should be ignored), the Merge Fields from both the Bib Dup and Auth Dup Detection profiles impact which fields from the existing bib record are retained.

    Defect Status

    Issue VYG-8004 is currently in Development.

    Replication Steps

    1. Find existing record in the db with, for example, 035 and 040 fields

    2. Take specific note of the 035 and 040 fields in this record

    3. Create a Bib Dup Detection profile with Duplicate Handling set to Merge that includes some Merge Fields, but NOT 035 and 040 

    4. Create an Auth Dup Detection profile with Duplicate Handling set to Merge that INCLUDES 035 and 040 

    5. Create a bulk import rule that includes the Bib Dup and Auth Dup Detection profiles you just created, and has match points that guarantee the existing record from step 1 will match the incoming record such that the incoming record overlays the existing record and retains some fields from the existing record 

    6. Bulk import a file with a record that should match your record from step 1 that includes different 035 and 040 fields not included in that existing record, using the bulk import rule specified in step 5

    Note that the incoming record overlays the original record, and not only are the fields specified in step 3 (the Bib Dup Detection profile Merge Fields) retained, so are the 035 and 040 fields that were specified in step 4 (the Auth Dup Detection profile Merge Fields).  

    Workaround

    If you delete the bib and repeat all steps *except* either remove the Auth Dup Detection profile from the bulk import rule completely, or remove the 035 and 040 from the Auth Dup Detection profile itself, you'll see that you get the expected results and while the fields specified in the Bib Dup Detection profile are retained, the 035 and 040 from the existing record are *not* retained.

     

     

    • Article last edited: 31-Aug-2022