MARS Bib Load

MARS Bib Loads

MARS Bib Duplication Detection Profile | MARS Bib Bulk Import Rules

Each week, on Sunday, our ITS department sends a file of approximately 3,000 bibliographic records to MARS (authority control service) in order to have the records updated with correct authoritative headings and also to have MARS create a file of authority records for auth records we do not yet own based on the authority headings associated with these bibliographic records. Within a few days (usually by Tuesday or Wednesday), MARS returns the file to us with the updated headings along with the file of associated authority records.

We receive an e-mail notification from MARS telling us the records are ready to be picked up from their server. Our ITS department retrieves the files and lets us know they have been placed on our server in the directory deleon:/m1/bulk/MARS-AUTHS. Once the files have been retreived and recorded in our logbook, ISP sends an e-mail to ITS with the following information for running the load:

File name: deleon:/m1/bulk/MARSH-AUTH/d040301.cc.bib (3, 769 records)

Script for Bulk Import:

From degama:/m1/voyager/yaledb/sbin:

$Pbulkimport -f/(file path)/(file name) -i MARSBIB -o MARSBIB

The -f flag signifies where the records are stored before loading (ITS will copy them to degama).

The -i flag signifies which Bulk Import rule is to be used.

The -o flag signifies the name of the load under which the record was added. This will be the "operator" found in the authority record history tab when viewing the record in the cataloging module.

After ITS runs Bulk Import to load the records, they must then run a .jar program to clear out the bib ids from ExportQ. The following information for running the .jar program is included in the initial e-mail we send to ITS:

Input file of bib ids: degama:/m1/voyager/yaledb/local/EXTRACTQ/extractq.log.MARS.d040229(filename of bib ids used to extract records)

Script for running .jar program:

java -jar MARSreload.jar /m1/voyager/yaledb/local/EXTRACTQ/extgractq.log.mars.D040229 lewis
(java -jar <name of program> <filename and path> <werver where database resides>)

ITS will send an e-mail to ISP once the process is complete with the log file name. We check a few records in ProdOrbis and ExportQ (to make sure the bibs ids are no longer queued for sending to MARS). We copy the stats at the end of the log and save them in a Word file of which we will send a copy of to the Authority Control Librarian. If any records were added as new instead of replaced we new to find the bib id in the log file and send that to the Authority Control Librarian as well.

To find bib id do a pattern search against the log file as follows:

from degama:/m1/voyager/yaledb/rpt:

$more (log file name)

Once the file is open, find the bib id by typing: /Adding Bib<return> - this will put you at the place in the log file where the bib was added. If you need to search for more than one, type /<return> and this will bring you to the next instance of the pattern.

Return to Database Loads Page