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.

Overview

For each record in a file, a single holding will be created. If you need a NET holding and a WID holding, the vendor can send two separate files, where most of the content is duplicated except for holding specific information.

• Migration note: This is a difference from Aleph, where multiple holdings could be created at once.

When reporting problems with a specific file load, please include the Job ID. 

This profile is designed for loading new records, not overlaying existing records. 

Input File Requirements

• Binary MARC (not XML)
• Character encoding UTF8

Matching

• Matching will be based on 035 (each 035 in a bib will be used to attempt a match)
• If an 001 and 003 are present in the vendor record, an 035 will be automatically created
• If there is no match on 035, the record will load as a new record
• If there is a match on 035, the new record will NOT load

Holding Creation (No Items Will Be Created)

Indicators from input field are copied, they don't need to add to mapping in profile. 

Subfields need to be explicitly identified, using a comma between (no spaces). 

These are the fields/subfields that have been configured to map to the holdings:  (haven't actually mapped all these yet)

• 852 $b and $c from the bib will be used to create a holding
• 007 (this can be in the bib instead if there are no print holdings)(is this needed at all if bib is coded for digital in 008/23?)
• 098 a,b,2  (will map to 852 h,i,2, and a fix routine will update the 852 1st indicator to 7)
• 506 a, f, 2, 5
• 538 a, j, l, u, 5
• 843 a, b, c, d, f, n, 7
• 856 u, z
• 909 k

Note: The order of fields in the Holdings Mapping is not important. It is okay of the order in the Sandbox profile is different than the one in Production.