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

    OCLC authority record overlay by oclc_server not working

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

    Description:
    I've configured the tables for loading OCLC records into Aleph and bib records are exporting and overlaying correctly. I am having difficulty getting authority records to overlay correctly--the export works fine but the overlay does not. When the record going into Aleph is already present in the system, Aleph adds the record as a new record instead of overlaying. I have looked at KB16384-770 and 16384-744 and I'm fairly sure the problem is with the spaces in the 010 fields of the authority records. I've made adjustments to the tables used but I'm unable to make the overlay work properly.

    Resolution:
    Looking at your ABC10 z11 010 entries with util f/4 I see this:

    01 z11_index \
    02 z11_rec_key \
    03 ind_code .......010
    03 filing_text .... N 0 0 0 0 0 1 7 9
    03 sequence_1 .....000000001
    02 z11_doc_number ...000000001
    02 z11_alpha ........L
    02 z11_text .........$$an^^00000179^
    new key = K, exit = Q, continue = RETURN


    01 z11_index \
    02 z11_rec_key \
    03 ind_code .......010
    03 filing_text .... N 0 0 0 0 0 3 6 8
    03 sequence_1 .....000055120
    02 z11_doc_number ...000055120
    02 z11_alpha ........L
    02 z11_text .........$$an 00000368

    You will note that the z11-filing-text is "double-byte": each character is taking two spaces. This was the way it was done in 14.2 but has not been since then.

    The 010 field is specified in tab00.eng as using tab_filing routine 11. When we input this z11_text to the abc10 util f/1/3 utility, we see a different result:

    Enter Filing Procedure (Q to quit)
    Enter values as defined in Col. 1 of tab_filing: 11
    Enter values D/N/F or Space:
    Enter text (Q to quit) : $$an^^00000179^
    IN -$$an^^00000179^ -
    Load: /tmp/utf_files/exlibris/aleph/u19_2/abc10/tab/tab_filing
    Load: /exlibris/aleph/u19_2/alephe/unicode/tab_character_conversion_line
    Load: /exlibris/aleph/u19_2/alephe/unicode/naco_diacritics
    Load: /exlibris/aleph/u19_2/alephe/unicode/unicode_case
    Load: /exlibris/aleph/u19_2/alephe/unicode/unicode_to_filing_01
    OUT -N 00000179

    Clearly an 010 field which is being translated in this fashion is not going to match the existing abc10 z11 index entry.
    You need to run p_manage_05 in abc10 to regenerate the existing z11 entries so they will be in a form which *will* match.

    In addition, you have this in tab_match:

    OCLC match_doc_uid T-010##

    it is trying to match:

    n^^81032755^

    against:

    n 81032755

    You need to specify this instead in abc10 tab_match:

    OCLC match_doc_uid I-010

    This will make the 010 field be processed by tab_filing -- which will produce a correct match.


    • Article last edited: 10/8/2013