• Article Type: General
• Product: Aleph
• Product Version: 17.01

Description:
We have tab_merge setup like this for OCLC:

OCLC merge_doc_overlay 02

tab_merge_overlay looks like this for the merge set '02':

02 1 N #####
02 1 Y 0359#
02 1 Y 099##
02 1 Y 501##
02 1 Y 59###
02 1 Y 690##
02 1 Y 790##
02 1 Y 791##
02 1 Y 793##
02 1 Y 949##
02 1 Y 98###
02 2 Y #####

When we export a record from OCLC to overlay an existing bib in Aleph, the export appears to work properly and we receive a message indicating such (for example, "Input docx merged into UTK01.001667636"). However, none of the new fields from the incoming record are added to the existing bib record.

Resolution:
We have had similar reports from other sites that have moved to Version 17. It appears that the OCLC overlay process treats the merging direction different than other processes.

For OCLC, 1 refers to refers to the record in the incoming load file, and 2 refers to the database record - exactly the opposite of the instructions given in the header of tab_merge_overlay.

This problem has been reported to development. In the meantime, other sites using OCLC import in Version 17 have solved the problem by changing the 1's in column 2 of tab_merge_overly to 2's, and vice versa - but only for the section being used by OCLC, of course. In your case, this appears to be section 02 (specified in column 1).

See also KB 8192-3353.

• Article last edited: 10/8/2013