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

    oclc server is not creating ADM records

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

    Description:
    When our librarians load new records through the oclc_server the ADM record is not being created.

    According to page 14 of 'How to Load OCLC Records into ALEPH - 18.01.pdf', Section 2 - General Work Flow of the OCLC Loader, step 5 - The OCLC loader created an ADM record in the ADM library.

    Our OCLC server log indicates 'Create new bib - SYS01.006627322' happened, but there was no ADM record created.

    In version 17 we would see the following in the oclc_server log:

    000000001 5016 Input docx was inserted into DB (docx SYS01.006626905)
    000000002 5024 New ADM created (docx MSU50.006626905)

    I've read through the 'How to', but I don't see where there are any different settings from version 17 to version 18. The matching and merging part works, its the automatic creation of ADM records on new SYS01 records that is not working.

    Resolution:
    This is a change in the 'generic_loader' (used by both the Marcive loader and the oclc_server) between V.17 and V.18. In V.18, the creation of the ADM record is bypassed if it's not needed. That is, if an item record is not being created.

    The documentation group has corrected the documentation and posted it on the doc portal.

    See KB 16384-36226 for a description of xxxx.def loader configuration files.


    • Article last edited: 10/8/2013