PREBULK CONFIGURATION FILES

For detailed information on creating configuration files for Prebulk, see page 52.1 in the Voyager Technical manual.

Configuration profiles are used by Prebulk to determine how records are to be processed before being loaded into ProdOrbis by the Bulk Import program. Configuration files must be written using the vi editor because they must be tab delimited. We store our configuration profiles in the following directory: (server): /m1/voyager/yale db/local/SCRIPTS/(configuration file name).

The following stanzas (in brackets) may be used in the configuration file:

[OVERRIDES]

CREATEMFHD= (yes or no)
DEFAULTCALLNO= (use this only if you are not pulling the call number from the bib record)
DEFAULTCALLIND= (can only designate the first indicator - used with above)
USE001FOR014= (puts record number from 001 in mfhd 014)
USE003FOR LOC=

[STRIP] (may strip tags alone or tags, indicators and subfields) - tab delimited

ex.)

910
980
981

[CALLTYPES] (specifies what indicator is to be used when creating an 852 tag in the mfhd) This option is used instead of using the parenthesis after the call number specified in the [LOCATIONS] stanza. We are not currently using this option for any loads.

[MFHD] (tag from bib records where mfhd information is drawn)

ex.)

049

[LOCATIONS] (tab delimited - location code from bib taken from (MFHDTAG} above <tab> Voyager location code - must be a valid code as defined in SYSADMIN <tab> hierarchy of call number fields with first indicator following in parenthesis - separated by comma, not tab.

ex.)

gdcg<tab>muddgdc,tab>(086(3),050(0),090(0)

[MAPPING] (this stanza is used to map subfields in the bib call number field to subfields in the mfhd tag - tab delimited.

ex.)

a 852b
b 852h
c 852i
k 852k
j 852m
v 866a

[008] (specifies how to create the 008 in the new mfhd)