Scope: This document explains the profiles that operators use to import authority records from the utilities.
Contact: Jim Leblanc
Date last reviewed: 10/23/01
Date of next review: February 2007
| Profile Name | Profile Code | Dupl. Handling | Cancel-
lation | Dupl. Repl. | Dupl. Warn | Field Definitions | Merge Fields | Field Weight |
|---|
| AuthImportConditional | AIMPCON | Add-
Conditional | None | 49 | 49 | A10A, A10Z, A35A, A35Z, ATID | N/A | 50 (all) |
| AuthMerge | AMERGE | Merge | None | 49 | 49 | A10A | 035 | 50 |
| AuthImportUnconditional | AIMPUNC | Add-
Unconditional | None | 100 | 100 | ATID | N/A | 100 |
Profile definitions and uses:
- AuthImportConditional
This profile explains how authority records are from the utilities when records are not added to the Cornell database through regular authorities procedures. The profile compares the authority record the operator is trying to import with records in the existing database using the following fields:
A10A (Auth LCCN (010a))
A10Z (Auth LCCN (010z))
A35A (Auth System Number (035a))
A35Z (Auth System Number (035z): Cancelled)
ATID (Authority Record ID)
With AuthImportConditional as the default profile, the following will happen:
If any of the fields above exactly matches any corresponding field in an existing record, the system will block the import. The Authority Dedupe Detection window will open, and the existing authority record will be highlighted in that window. The operator will have the option of backing out of the import attempt or overlaying the record (see AuthMerge below). [Note that dup detection can be overridden at any time by clicking the "Add as duplicate" button in the upper-right corner of the window.]
Import Conditional should be the default profile for all operators. In the Cataloging module, the authority import profile is selected under Options--General, and needs to be done on a client-by-client basis.
- AuthMerge
With ImportConditional as the default import/replace profile, Merge will be one of the operator options upon detection of a duplicate record. Merge can be used to replace an older version of an authority record with a more recent one, while retaining 035 fields from the older record, if the new record has not been or will not be added to the database by standard authorities procedures. The AuthMerge profile looks for an exact match on an 010 $a. If the 010 $a of the imported record does not match on an 010 $a in an existing record, the imported record will be added as a new record.
AuthMerge is used as the standard import/replace profile for bulk import of authority records.
- AuthImportUnconditional
With the AuthImportUnconditional profile, imported authority records are added to the database regardless of whether duplicates of any kind are present (e.g.., exact duplicates, 010 matches, 1XX matches, etc.). This profile should be used only in special, controlled circumstances for high-speed bulk import.
