OCLC Reclamation

I contributed to the University of Toronto OCLC Reclamation project by:

  1. Using MySQL to identify all records which were experiencing specific errors (e.g. Invalid relationship – when 036 is present, then $b in 036 must be present).
  2. Batch downloading the local files in MarcEdit, editing the files to fix the OCLC error
  3. Providing a fixed file to my coworker who had uploading privileges with the catalogue keys
  4. Updating the MySQL table with a FIXED error status column

Additionally, where it was necessary, I manually compared OCLC records which were slated to be uploaded to replace local records which had been identified as sparse. When manually comparing, I confirmed that all records:

  • Had a 001 field
  • Had a matching or very similar 100 or 110 field to the sparse record
  • Had a matching or very similar 245 field to the sparse record
  • Had a matching or very similar 300 field (all records were for print resources)
  • Confirmed that information in the 260 was transferred to the 264 field where the record was RDA compliant
  • Confirmed that the information in the 440 field was moved to 490 to match current MARC standards
  • Confirmed that the language of cataloguing was English (040 $beng)