This profile is for loading order records from vendors
The label in Data Exchange is (3) Load b & o, match 001 [acq3]
On the Sierra server it is called m2btab.acq3
Table of Contents
Bib and order records will be created. |
Match on the BIB UTIL number. Code:
|
Code:
|
Variable (retain both incoming and target data)
Variable (retain only target data, ignore incoming data)
Fixed
Code:
|
Bib: tapeb Item: mdlholddum Order: _o The template settings only take effect if that field is not defined in any other way by the record load. Templates only effect fixed fields when loading records with load profiles. Prompting for fields does nothing when loading records with load profiles. Code:
|
These commands will override defaults in the bib record. This is rarely used. recs = Load Profile
Code:
|
This load will not set the CAT DATE. Records should not get a CAT DATE until they get an item attached. Code:
|
Processed by m2bmap.sky translation map. This translation map removes OCLC prefixes from 001 field. Other prefixes are left in place. SkyRiver prefix is left in place. If there is only a number with no prefix, the word “prefix” is added as a prefix. Code:
m2bmap.:
|
If the target record is in field group v LOCAL INFO and includes any of these strings:
then the field is protected. No incoming 856 field with “|2pika” will load in that case. All other 856 fields are not protected. They will be overlaid from the incoming record. If there is no 856 in the incoming record, they will be deleted from the target record. Code:
m2bmap.art
m2bmap.not
|
FIXED FIELDS
VARIABLE FIELDS
|
|
Every load will create one dummy item record based on the mdlholddum item template. There is no means to alter this dummy item. Code:
|
Creates one order record with every load. Order record data will be created based on the 960 and 961 fields.
|
|