Skip to main content
ExLibris

  • Subscribe by RSS
    • Aleph
    Ex Libris Knowledge Center

    Batch merge vs. GUI Cataloging merge

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    Are the same merge/overlay/fix routines used for a batch mode (p_manage_36/p_manage_18) and the interactive GUI overlay? Or are these different.

    I've had a person in Authorities claim that interactive overlay worked properly, keeping certain fields intact. But, I've not tracked down what merge routine that might have been which would have kept those fields safe. They were added to tab_merge_overlay, but then what merge routine might have been used that would have left them intact interactively?

    Resolution:
    As described in KB 3249, the GUI Cataloging overlay process looks for a MERGE label in tab_fix. It then uses the relevant tab_merge and tab_merge_overlay parameters to perform the merge.

    When the p_merge_type parameter is specified, p_manage_18 reads that label directly in tab_merge. It does not use the tab_fix MERGE label.

    • Article last edited: 10/8/2013
    //Feedback