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

Description:
We have discovered that extra blank characters at the end of the 010 are being imported as carets. Since our existing authority records have no carets, the records do not overlay. Some examples of OCLC records that appear with trailing carets in Aleph: 777000, 777001, 777005

To address this problem, on Friday I added another line to the abc01 $data_tab/import/addupdn.fix.

Resolution:
ALEPH's oclc_server first processes the tab_fix (in it's order), then matches, then merges. Per your sequence, it first converts the 010's spaces into carets (^), then modifies that into a non-space.

In the case of n88293986 it matched, in the the case of 010 n88293986 it matched, but in the the case of 010 n 85213275 (sysno 000555003) it will not.

Accordingly I changed the 010 REPLACE-STRING ^, to have after the comma a space (that would retain the space between the n and the 85213275) to enable a match.

• Article last edited: 10/8/2013