(B) Load a non-OCLC MARC file [msc]

This is a load profile for loading non-OCLC bibliographic MARC records
The label in Data Exchange is (B) Load a non-OCLC MARC file [msc]
On the Sierra server it is called m2btab.msc

Table of Contents

1 Details
2 Related Documentation

Details

Bib and item records will be created.

First: 020a

Second: 022

This will first look for matches in 020a. If it does not find any matching 020a fields, then it will check 022.

Code:

/^999||t|0|10| | |0|n|G|0|#com="ov"@ov_tag="i(020)v:i(022)i"

0 matches: Insert new bib

1 match: Attach item only (no overlay, insert 995)

2 matches: Reject

Code:

|||0|0| | |0|n|G|0|@ov_action="c"

All fields are protected because this loader will never overlay a bib

It will only insert a new bib or attach an item to an existing bib (and insert a 995)

Bib: tapeb

Item: tapei

These are the default templates in Marmot loaders. The template settings only take effect if that field is not defined in any other way by the record load.

Code:

/^999||o|0|20| | |0|n|G|0|#com="dflt"@dflt="tapeb,tapei"

These commands will override defaults. This is rarely used.

recs = Load profile
bn = bib location
ct = Cat Date
b1 = Bib Lvl
b2 = Mat Type
b3 = Spec’l Use
la = Language
cy = Country

Format:

949 \\$a*recs=msc;bn=cu;ct=01-18-2021;b1=m;b2=a;b3=w;la=spa;cy=cou;

Code:

/^999||z|0|10| | |0|n|G|0|#com="recs"@recs="msc"
/^999||a|0|30|b| |26|n|N|0|#com="bn"
/^999||c|0|8|b| |28|n|N|0|#com="ct"
/^999||d|0|1|b| |29|n|N|0|#com="b1"
/^999||e|0|1|b| |30|n|N|0|#com="b2"
/^999||f|0|1|b| |31|n|N|0|#com="b3"
/^999||g|0|3|b| |24|n|N|0|#com="la"
/^999||k|0|3|b| |89|n|N|0|#com="cy"

Will never change a CAT DATE because it will not overlay. If a new record is inserted because there are no matches, then it will set CAT DATE to today.

Code:

|||0|0| | |0|n|G|0|@cdate="y"

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.

Code:

001||%|0|0|b|o|0|y|N|0|%map="m2bmap.sky"

m2bmap.sky:

@case=true
@stop_on_map=true
^(001)$0ocl70*([1-9][0-9]*)$1|\0\1
^(001)$0ocm0*([1-9][0-9]*)$1|\0\1
^(001)$0ocn([1-9][0-9]*)$1|\0\1
^(001)$0on([1-9][0-9]*)$1|\0\1
^(001)$0( *[a-zA-Z].*)$1|\0\1
^(001)$0(.*)$1|\0prefix\1

If the target record is in field group v LOCAL INFO and includes any of these strings:

|2pika
|2vufind
|2image
|2Pika
|2VuFind
|2Image

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:

856||+|0|0|b|v|0|y|N|0|%map="m2bmap.art" 
856||+|0|0|b|y|0|y|N|0|%map="m2bmap.not"

m2bmap.art

@delimiter=~
@case=true
@stop_on_map=true
(.*|2pika.*)$0~\0
(.*|2vufind.*)$0~\0
(.*|2image.*)$0~\0
(.*|2Pika.*)$0~\0
(.*|2VuFind.*)$0~\0
(.*|2Image.*)$0~\0
.*~

m2bmap.not

@delimiter=~
@stop_on_map=true
@case=true
(.*|2pika.*)$0~
(.*|2vufind.*)$0~
(.*|2image.*)$0~
(.*|2Pika.*)$0~
(.*|2VuFind.*)$0~
(.*|2Image.*)$0~
(.*)$0~\0

FIXED FIELDS

Incoming	Output

Incoming	Output
008 Language	LANG fixed field
008 Country	Country fixed field
Leader BLvl	Bib Lvl fixed field
Leader Type of Record	Mat Type fixed field

VARIABLE FIELDS

Incoming field	Output field group tag	Notes

Incoming field	Output field group tag	Notes
001	o	OCLC prefix removed Other prefixes left in place
002 - 007	y	The incoming 005 is retained. Sierra does not change the 005. It should reflect the date the record was last updated where ever the record came from.
008	y	Modified to add some fields from Leader, these fields returned to Leader on export
009	y
010	l
011	NOT LOADED
013 - 018	y
019	o
020 - 024	i
025	y
026	NOT LOADED
027 - 028	i
029	NOT LOADED
030 - 049	y
050 - 084	j
085	NOT LOADED
086	g
087	NOT LOADED
088	j
089	NOT LOADED
090 - 099	j
100 - 111	a	Exclude subfield w
112 - 129	NOT LOADED
130	t	Exclude subfield w
131 - 209	NOT LOADED
210	y
211 - 222	u
223 - 239	NOT LOADED
240	t	Exclude subfield w
241 - 243	u
244	NOT LOADED
245	t
246 - 247	u
248 - 249	NOT LOADED
250	e
251 - 253	NOT LOADED
254 - 257	y
258 - 259	NOT LOADED
260 - 262	p
263	y
264	p
265	y
266 - 269	NOT LOADED
270	p
271 - 299	NOT LOADED
300 - 399	r
400 - 490	s	Exclude subfield w
491 - 499	NOT LOADED
500 - 589	n
590 - 599	NOT LOADED
600 - 689	d	Exclude subfield w
690 - 691	v	Exclude subfield w
692 - 699	d	Exclude subfield w
700 - 711	b	Exclude subfield w
712 - 719	NOT LOADED
720	y	Exclude subfield w
721 - 729	NOT LOADED
730 - 740	u	Exclude subfield w
741 - 751	NOT LOADED
752 - 755	y
756 - 759	NOT LOADED
760 - 777	q
778 - 779	NOT LOADED
780	x
781 - 784	NOT LOADED
785	z
786	y
787	w
788 - 799	NOT LOADED
800 - 811	s	Exclude subfield w
812 - 829	NOT LOADED
830	s	Exclude subfield w
831 - 839	NOT LOADED
840	s	Exclude subfield w
841 - 855	y
856	y or v	856 loads into FGT v if the string “\|2pika” is present in the field. However, the field is protected so this would only load if there were not already a matching field in the record. If there is already a \|2pika field, then this will not load. Otherwise 856 loads into FGT y.
857 - 865	NOT LOADED
866	h
867 - 868	y
869 - 879	NOT LOADED
880	y
881 - 897	NOT LOADED
898	y
899	NOT LOADED
900 - 906	y
907 - 908	NOT LOADED
909 - 937	y
938	NOT LOADED
939 - 947	y
948	NOT LOADED
949	Item d	Move to 945 in item record, FGT d
950 - 959	y
960 - 961	NOT LOADED