MARS Auth.ccr Loads

MARS AUTH.CCR LOADS

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 CJK bibliographic and authority record files are ready for pick-up from their server. This notice is usually sent by the second week of the month. The two files are processed separately.

The authority files use the naming convention, v02m12.ccr.auth. These files are loaded in the same manner as the MARS Auth Notification files. The ccr.auth files should always be loaded after the MARS Auth Notification records which were received during the same week. They are one month behind the Notification records in the naming convention (ie. the MARS Auth Notification file v02m12.auth is loaded before the MARS Auth.ccr file v02m11.ccr.auth). Once these files have been retrieved and recorded in the logbook, DPA sends an e-mail to ITS letting them know that the auth records are ready to be loaded to production via Bulk Import using the MARS Authority Bulk Import Rules.

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

$ Pbulkimport -f /m1/bulk/MARS-AUTH/v02m12.ccr.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 DPA that the job has run and will include the name of the log file that contains the job output. DPA 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 DPA is satisfied that the records have loaded correctly, the output stats are sent to the Authority Control Librarian. These records should all load as new or merged authority records. Once in a while there may be more than one matching authority record found in the database. When this happens, the incoming record is discarded. Discards will be reflected in the output stats from the load. The discard log file should be sent to the Authority Control Librarian as well so she can import the discarded record via the cataloging module and decide which record should be overlaid.

Return to Database Loads Page