Department Manual
Bulkimport

Bulkimport is a process by which large groups of bib records can be added to the Voyager database. Bulkimport has a variety of options, and this document is intended to cover the basics of the bulkimport process and some of the different options that K-State Libraries has used. This document covers bulkimport as it works in Voyager 2001.1. For more information on the bulkimport process, see the Voyager Technical Manual.

Note: In order to be able to run a bulkimport job, the staff member needs to be authorized to login to the K-State Libraries Voyager server. If a staff member needs to have records loaded and is not authorized to logon to the server, he/she will need to contact the appropriate staff in the Technical Services Dept. or the K-State Libraries Voyager System Administrator to have the records loaded.

The following table lists some of the commonly used bulkimport profiles currently in use at K-State Libraries. This is not a comprehensive list. New bulkimport profiles are set up in the Voyager System Administration client.

1. FTP file of bib records to the Voyager server and place them in the /m1/voyager/ksudb/sbin directory. This can be done with any FTP client, such as Winsock FTP.

2. Logon on to the Voyager server. After logging in, you will be at the following prompt: /var/local/endeavor/home/voyager

3. Change directories to the /m1/voyager/ksudb/sbin directory. To do this, at the prompt type: cd /m1/voyager/ksudb/sbin

4. Enter the command for bulkimport at the /m1/voyager/ksudb/sbin prompt. To do this, at the prompt type Pbulkimport followed by the necessary parameters. The following are parameters for the bulkimport command:

-f	File name for the file of bib records (required)
-i	Import code. This comes from the individual bulkimport rules set up in System Administration. (required)
-o	Operator name (not required)
-l	Location name for the cataloging location, not the MFHD or item location (not required)
-b	Beginning record number, the number of the first record in the file to be imported. This only needs to be used if a portion of a file is being loaded. If loading a file of interleaved bibs and MFHDs created by prebulk, use the record number of the first bib record to be loaded. (not required)
-e	Ending record number, the number of the last record in the file to be imported. This only needs to be used if a portion of a file is being loaded. If loading a file of interleaved bibs and MFHDs created by prebulk, use the record number of the last bib record to be loaded. (not required)
-m	Loads MFHDs when there is a single file of interleaved bibs and MFHDs created by prebulk. This is not used when loading just a file of bib records, but must be used when loading a file of interleaved records. (not required)
-a	MFHD location code. Will set all incoming MFHDs to the location specified, if MFHDs are being created. In most instances, K-State Libraries is not using this option, and is instead using the values defined by the bulkimport rule being used. (not required)
-r	Delete MFHDs, used to delete specified MFHDs from the Voyager database. See the Voyager Technical Manual for more information. (not required)
-x	Delete bibliographic records. Used to delete bib records in the Voyager database that match records in the input file. See the Voyager Technical Manual for more information. (not required)


Examples of bulkimport commands

Pbulkimport -f bibfile -i addcond (Loads the file named bibfile and uses the bulkimport rule of addcond to load the records.)

Pbulkimport -f bibs2 -i shelf -o ajones (Loads the file named bibs2 and uses the bulkimport rule of shelf to load the records. All records loaded will have the operator ajones in the record history.)

Pbulkimport -f kstu1011 -i gpship -b 1 -e 250 (Loads the file named kstu1011 and uses the bulkimport rule of gpship to load the records. Only records 1 through 250 are loaded.)

Pbulkimport -f opie -i addcond -m (Loads the file opie, an interleaved file of bibs and MFHDs created during Prebulk. Uses the bulkimport rule of addcond to load the records. Loads both bibs and MFHDs, using the MFHDs created during prebulk.)



5. After the bulkimport job is run, several files related to the job are created in the /m1/voyager/ksudb/rpt directory. The most important of these files is the log file, which provides a summary of the job and notes any problems with individual records. To view the log, change directories to the /m1/voyager/ksudb/rpt directory. To change directories, type at the prompt: cd /m1/voyager/ksudb/rpt

6. When the directory has been changed to /m1/voyager/ksudb/rpt, do the list command to see all the files in the directory. To do the list command, at the prompt type ls.

7. The log file will be named log.imp.YYYYDDDD.TTTT, with YYYYDDDD.TTTT representing the year, day, and time that the job was started. For example, the log for a job started on Oct. 11, 2001, at 2:35 p.m. will be log.imp.20011011.1435.

8. To view the entire log, at the prompt type more (file name). For example, to view the entire log in the example in the previous step, type: more log.imp.20011011.1435

9. To view just the end of the log file, which contains the job summary, type cat (file name). For example, to view the end of the log in the example in the previous step, type: cat log.imp.20011011.1435

10. Records which are not added during the bulkimport process are written to the reject file, which has the same day/time stamp as the related log file. For example, the reject file for the log file in the steps above would be reject.imp.20011011.1435. The records are stored in that file in their original MARC format. Records are generally rejected if they are duplicates of records already in the K-State Libraries database. If the file needs to be viewed, it can be FTP'd to a file on the Libraries' LAN or an individual's computer. It can then be viewed the same way a file of any other bib records are viewed in the Cataloging client.