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

    OCLC Export does not overlay

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

    Description:
    We are having a problem with the OCLC export when there is an existing record in ALEPH.
    The OCLC export worksOK for new records. But does not overlay the existing record. When checking with p-manage-36, the match is found. What is wrong?

    Resolution:
    The OWN field was not defined in Col.2 of tab_loader, while the record in the database had an OWN field.
    After matching according to the tab_match setting, the system filters the records by their OWN field.

    See Chapter 2 of the "How to Load OCLC Records into ALEPH - 19.01" document:

    >> 2 General Work Flow of the OCLC Loader

    After the OCLC server is running, the OCLC loader handles records as follows:
    1. The loader looks for the tab_loader table which contains the holding code
    from field 049. The ADM library where tab_loader0 resides is the ADM
    environment for the loading.
    2. The loader looks for matching records using the section defined in tab_oclc
    (col. 9).
    3. The loader filters the matched records according to the owner group from
    tab_loader, col. 9. It leaves only those records which have an OWN field that
    belongs to the OWN group as defined in tab_loader.
    If there is more than one match, an error is returned.
    If there is one matched record, then the loader merges the new loaded record with
    the existing one, adds a new OWN field, and saves it.
    4. If there is no matched record, then the loader creates a new bibliographic
    record, adds an OWN field, and then executes the special fix routine defined
    in col. 4 of tab_oclc.
    <...> page 17 <...>

    Additional Information

    OCLC


    • Article last edited: 10/8/2013
    • Was this article helpful?