MARC.pm & Prebulk

Process

Overview

Table 1: Process Overview
Step	Type of Processing	Sample Input Record(s)	Relevant Program or Config File	Sample Output Record(s)
1	MARC.pm	bib.0	netlib01.pl	bib.1
2	Prebulk	bib.1	prebulk.cfg	bib.2 + mfhd.2
3	MARC.pm	bib.2 + mfhd.2	netlib03.pl	bib.3 + mfhd.3
4	Bulk Import	bib.3 + mfhd.3	Bulk Import Rules	Voyager record
Note: Actual input and output files are in raw MARC format. The sample bib and MFHD records displayed here have been parsed into ascii/html format for illustrative purposes.

Download a tarball containing netlib01.pl, netlib03.pl and prebulk.cfg.
(Cutting and pasting may introduce errors into the files.)

Step 1: First pass through a MARC.pm script

netlib01.pl file.0 file.1

In this step, we took the file of bib records as received and ran them through our first Perl/MARC.pm script, netlib01.pl. We added a 099a field containing the generic local call number ("Web Access") that UTA uses for electronic resources. We also extracted the unique URL from the 856u, appended it to our institution's EZproxy URL, and then stuffed it all back in the 856u. In addition, we replaced the 856z with our own customized public note.

Step 2: Creating MFHDs with Prebulk

Pprebulk -i file.1 -o file.2 -c prebulk.cfg

The output file of bib records from step 1 is massaged with Prebulk to create an interleaved file of bibliographic and MFHD records. Instead of using Prebulk to map over unique call numbers from the bib record, we used it to map over the unique 856u field into the MFHD. This required a little creativity in setting up the prebulk configuration file. The no-longer-needed 856 in the bib was stripped out. We also tweaked the MFHD 008 to change the default values of some of the data elements relevant to netLibrary holdings (e.g. b for "will not lend" in position 20). [convenient MFHD 008 cheatsheat]

Step 3: Second pass through a MARC.pm script

netlib03.pl file.2 file.3

All we did with netlib03.pl was add the desired indicators to the MFHD's 856 tag (since we couldn't figure out how to do it in any of the earlier steps).

Step 4: Importing into Voyager with Bulk Import

Pbulkimport -m -f file.3 -i import_code

Now our old friend Bulk Import could be used to load the records into Voyager. After creating some "netLibrary" Bulk Import Rules, we did a trial load of ten records. The log file indicated a successful load. After our technical and public services staff reviewed those records (and suggested some changes) we began to import larger files.