Table of Contents

Details

Bib and item records will be created.

“o” index

Looks for a match in the o index, which includes 001 and 019.

0 matches: Insert new bib

1 match: Overlay existing bib

2 matches: Insert new bib

Variable (retain both incoming and target data)

  • Field group: h LIB HAS

  • Field group: k TOC DATA

    • MARC tags: 970, 971

  • Field group: m LOAD NOTE

    • MARC tags: 995

  • Field group: n NOTE

    • MARC tags: 583

  • Field group: v LOCAL INFO

    • MARC tags: 590

  • Field group: y MISC

    • MARC tags: 948, 958

Variable (retain only target data)

  • Field group: v LOCAL INFO

    • MARC tags: 590, 690, 691, 856

Fixed

  • SPEC’L USE

Code:

@ov_protect="b=V0123456789hk(970,971)m(995)n(583)v(590,69.,856:d)y(948,958)F31"

Bib: cucuege

Item: cuege

The template settings only take effect if that field is not defined in any other way by the record load.

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=msgov7;bn=cu;ct=01-18-2021;b1=m;b2=a;b3=w;la=spa;cy=cou;

This will always set the CAT DATE to today.

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

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

001

o

OCLC prefix removed
Other prefixes left in place

002 - 007

y

The incoming 005 is retained. Sierra does not change a 005. It should reflect the date the record was last updated where ever the record came from.

008 - 009

y

Modified to add some fields from Leader, these fields returned to Leader on export

010

l

013 - 018

y

019

o

020 - 024

i

025

y

027 - 028

i

030 - 049

y

050 - 084

j

086

g

088

j

090 - 099

j

100 - 111

a

130

t

210

y

211 - 222

u

240

t

241 - 243

u

245

t

246 - 247

u

250

e

254 - 257

y

260 - 262

p

263

y

264

p

265

y

270

p

300 - 399

r

400 - 490

s

Exclude subfield w

500 - 589

n

600 - 689

d

Exclude subfield w

690 - 691

v

Exclude subfield w

692 - 699

d

Exclude subfield w

700 - 711

b

Exclude subfield w

720

y

Exclude subfield w

730 - 740

u

Exclude subfield w

752 - 755

y

760 - 777

q

780

x

785

z

786

y

787

w

800 - 811

s

Exclude subfield w

830

s

Exclude subfield w

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.

866

h

867 - 868

y

880

y

898

y

900 - 906

y

909 - 937

y

939 - 947

y

949

Item d

Move to 945 in item record, field group tag d

950 - 959

y

962 - 987

y

990 - 994

y

995

m

Ignores incoming field and loads text “Loaded with m2btab.msgov4 in this month”

996 - 997

y

999

y

Notes

011

012

Only used by CONSER

026

Only used in rare book cataloging

029

OCLC uses this for non-OCLC control numbers

085

Synthesized Classification Number Components

087

089

112 - 129

131 - 209

223 - 239

244

248 - 249

251

Only used in rare book cataloging

252 - 253

258 - 259

266 - 269

271 - 299

491 - 499

590 - 599

Reserved for local notes

712 - 719

721 - 729

741 - 751

756 - 759

778 - 779

781 - 784

788 - 789

812 - 829

831 - 839

857 - 866

869 - 879

881 - 897

899

907 - 908

Used to store local record numbers when records are exported

Can be confusing if these are loaded into the system and stored, they may be exported again and will not be accurate.

938

Often filled with junk from other local systems

948

Used to record our authority vendor loading information

960 - 961

Used for creating order records, not needed to live in bib records

988 - 989

998

The load will create one item record for each 949 1 field included in each MARC record.

Element

Incoming

Target

Call number MARC tag

subfield z

MARC tag

Call number prefix

subfield d

subfield d

Classification number

subfield a

subfield d

Cutter number

subfield b

subfield b

Call number suffix

subfield e or k

subfield e or k

Volume

subfield c

volume field

Local note

subfield f

variable local note

Copy number

subfield g

fixed copy number

Agency

subfield h

fixed agency number

Barcode

subfield i

variable barcode field

Price2

subfield j

variable price2 field
(not currently used)

Location

subfield l

fixed item location field

Pop up circ message (variable)

subfield m

variable circ message field

Internal note

subfield n

variable internal note field

OPAC message

subfield o

fixed OPAC message field
(only works in classic catalog)

Price

subfield p

fixed price field

Icode1

subfield q

fixed Icode1 field

Icode2

subfield r

fixed Icode2 field

Status

subfield s

fixed status field

Itype

subfield t

fixed Itype field

Pop up circ message (fixed)

subfield u

fixed circ message field

eContent

subfield w

variable eContent field
(used by Pika for electronic resources from Sierra, rarely used)

  • Format:

949 \1$z090$dPRE$cE842$b.D28 2003$eSUF$h13$i1050003456789$lculmb$mMESSAGE$t18

Top of page

Related Documentation

Top of page