MARS Authority Notification Load

MARS AUTHORITY NOTIFICATION

MARS Authority Duplication Detection Profile | MARS Authority Bulk Import Rules

Once a month we receive an e-mail notification from MARS letting us know our MARS Authority Notification authority and delete files are ready for pick-up from their server. This notice is usually sent by the second week of the month.

Once the files have been retrieved and recorded in the logbook, ISP sends an e-mail to ITS letting them know that the authority records are ready to be loaded into ProdOrbis via Bulk Import . We are in the process of developing a method for handling the delete records..

ITS loads the auth records using the following Bulk Import script run from
degama: /m1/voyager/yaledb/sbin:

$ Pbulkimport -f /m1/bulk/MARS-AUTH/v03m01.auth -i YLMARAU -o MARSAUTH

The -f flag signifies where the records are stored before loading.
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.

Once the files have been loaded, ITS will notify ISP that the job has run and will include the name of the log file that contains the job output. ISP then checks the output stats to see that the file has loaded as expected and checks some records in the ProdOrbis cataloging module to assure the records have loaded correctly.

Once ISP is satisfied that the records have loaded correctly, the output stats and the log file of discards* are sent to the Authority Control Librarian for resolving duplicate records in the database and importing the new record into ProdOrbis.

*Some records from the MARS Authority Notification file are sent to a discard file because Endeavor's Duplicate Detection program found more than one match in our database and was unable to determine which record to overlay. To view the discarded auth records, from the /m1/voyager/yaledb/rpt directory, type: more discard.imp.20030108.1433 (instead of log.imp.20030108.1433) at the $ prompt. The discard file can be transferred to a PC via Secure File Tranfer and then sent as an e-mail attachment to the cataloger. These records can easily be imported into Voyager through the cataloging module.

Return to Database Loads Page