Staff upgrade bib OCLC number match (MRC)



REMEMBER: Only designated staff members are permitted to run jobs. Refer to the matrix at Jobs & Batch Processes to see which staff members are approved to run which jobs.

Usage

This import profile is designed for records downloaded from OCLC.

This profile will merge/overlay the existing Alma record and should be used with caution. No other matching criteria will be evaluated other than OCLC number.  The merge routine used is the same one that is used for OCLC WorldCat Updates (see the "Prefer OCLC" column). 

Requirements

  • Vendor records must be in UTF8 encoding format. Non-Latin fields should be in 880 pairs. 
  • Input file should be in MARC binary format (not MARCXML)
  • Vendor record must have either:
    • 035 $a(OCoLC)... If it does not match to an existing Alma record it will not load. 
    • OR
    • Both 001 with OCLC number and 003 with (OCoLC). Alma will construct the appropriate 035 based on these values.

(warning)  Notice: Presence of both 035 $a(OCoLC) and the 001/003 (OCoLC) combination will bring in an extraneous 035 field with the $a content, because Alma creates a new 035 based on the 001/003. This import profile uses a special norm rule to remove the 003 prior to the load, so that only the existing 035 from OCLC will be created. It is assumed that the record being imported with this profile come from OCLC and have the 035 already. If this is not the case this profile should not be used. Contact LTS with any questions. 

Results

  • No inventory will be created. 
  • If a record is locked by a staff member it will not be overlaid.
  • The incoming record will overlay the Alma record, with certain fields being protected. See list of protected fields here: https://harvardwiki.atlassian.net/wiki/x/6aGVAgE

Example use case

  • You have a set of Alma records, whose OCLC numbers are correct, and you would like to download updated records from Connexion to overlay the older ones in Alma.