Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »



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. The merge routine used is the same one that is used for OCLC WorldCat Updates (see the "Prefer OCLC" column). 

Due to the fuzziness of the matching, this profile should be used with great caution to upgrade bibs that lack OCLC numbers. 

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 recordd 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. 

Matching

This profile uses the "Multi-step match method" which will perform a sequence of tests. If a bib fails to match on the first test, Alma moves on to the second test, then third. If there is still no match, the record is not loaded. 


More details on the Alma routines listed below may be found on the ExL site. 

TestAlma routine nameSummary
1Unique OCLC Identifier Match MethodMust match on OCLC number in 035 $a or $z
2

ISBN (exact subfield match)/ 024 / 035 Match Method

(or ISSN version of serials)

  1. Incoming 020 $a must match Alma 020 $a, or
  2. Incoming 020 $z must match Alma 020 $z, or
  3. 024 or 035 match
3

Title Statement Extended Fuzzy Non-Serial Match Method

(or Serial version)

  1. 020 match, any subfield (or 022 for serials)
  2. LCCN, 035 match
  3. Author, as taken from any of the 1XX/7XX fields, AND title as taken from any of 245 $a, 210 $a, 246 $a. 
  4. If incoming bib lacks any author, there is a test for a title match using 245 $a, 210 $a, 246 $a. 


In the event that multiple matches are found for any step, Alma will choose the bib that was added most recently 

Results

  • No inventory will be created. 
  • If a record is locked by a staff member it will not be overlaid.
  • The incoming record will upgrade 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 that lack OCLC numbers and you wish to upgrade them with copy from OCLC. 


  • No labels