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

    No 001 field (with ALEPH system number) created when loading OCLC records

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

    Description:
    We are currently loading OCLC promptcat records into the catalog. These titles are coming to us shelf ready. Our current process is to load them into Aleph and when they get received they will be placed on our "What's New" shelf.
    Recently we stopped having a cataloger save each record in Cataloging, and noticed that these records have an 001 with the OCLC record number (ie. 001 ocm84008935).
    We were wondering if there is a way for the Aleph system number to go into the 001 without us having to touch the records (save to server)?

    Resolution:
    As described in KB records 8192-2153 and 4137, ALEPH does not require that BIB records have an 001 field. But if you want to have one, then ...

    Is the 035 being created properly? (Site confirmed that it is and 001 is the only problem.)

    The automatic updates which the system does when a record is saved to the server by a cataloger are determined by the INS and INS2 lines in the ./xxx01/tab/tab_fix. The 001 is being added by this line:

    INS2 fix_doc_001

    If the promptcat records are being processed by the oclc_server, you can add this line at the end of the OCLC lines in tab_fix:

    OCLC fix_doc_001

    (This worked.)

    FAQ

    Additional Information

    faq


    • Article last edited: 10/8/2013