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

    Merging direction is the opposite of what was expected

    • Article Type: Q&A
    • Product: Aleph
    • Product Version: 18


    In ./xxx01/tab/tab_merge_overlay column 2 is defined in the following way:

    ! COL 2. 1; NUM{1,2}; ;
    ! Merging direction;
    ! Merging direction:
    ! 1: refers to the database record
    ! 2: refers to the record in the incoming load file

    When merging 2 records, one from an input file and the other from the database, the direction of the merge acts the opposite. Why?


    See also header of ./xxx01/tab/tab_merge

    ! Note: when running file-99, file-93, manage-18
    ! and oclc_server with merge_doc_overlay or
    ! tab_merge_adv_overlay, the preferred
    ! record is the record in the incoming load file.
    ! In order to change direction add preferred_doc_switch
    ! to tab_preferred; it changes the direction
    ! and switches between the preferred and
    ! the non-preferred records.

    This applies also to Advanced Generic Vendor Records Loader (file-90) and also Load OCLC Records (file-93)

    Additional Information

    Merge direction can be changed according entry in ./xxx01/tab/tab_preferred

    Category: Cataloging (500)

    Subject: Importing records (500)

    • Article last edited: 10/8/2013