Library Technical Services

Bibliographic Import/Replace Profiles

Scope: This document explains the various profiles used by operators to import bibliographic records into the Voyager database from the utilities.

Contact: Jena Bakula

Date last modified: 03/27/08

Date of next review: February 2009

---

Profile Name	Profile Code	Dupl. Handling	Cancel- lation	Dupl. Repl.	Dupl. Warn	Field Definitions (Match Points)	Merge Fields	Field Weight
Acq Conditional	ACQCON	Add-Conditional	None	49	49	010A, 019A, 020N, 020R, 022A, 022Z, ISB3	N/A	50 (all)
BIBReplace	BIBREPL	Replace	None	49	49	BBID	N/A	50
Import Conditional	IMPCON	Add-Conditional	None	49	49	010A, 019A, 020N, 020R, 022A, 022Z, 0350, 2450, ISB3	N/A	50 (all)
Import Unconditional	IMPUNCON	Add-Unconditional	None	60	60	0350	N/A	50
CJKScriptMerge	CJKMERGE	Merge	None	49	49	0350	902,903,948,957	50
ISBNtesting	ISBNTEST	Add-Conditional	None	49	49	020N, 020R, ISB3	N/A	50 (all)
LCReplace (in RD SysAdmin)	LCREPL	Replace	None	49	49	010A	N/A	50
MARCadiaMerge	MARCMERG	Merge	None	49	49	BBID	902,903,948,957	50
MarciveMerge	MCVMERGE	Merge	None	49	49	0350	035,520,653,899,902,903,948,975	50
MarciveMerge2	MCVMERG2	Merge	None	49	49	010A	035,520,653,899,902,903,948,975	100
Merge	MERGE	Merge	None	49	49	0350	035, 505, 520, 653, 853, 854, 855, 856, 863, 864, 865, 899, 902, 903, 905, 948, 949, 957, 975	50
MIT Conditional	MITCON	Add-Conditional	None	49	49	0350	N/A	50
NetLibConditional	NETCON	Add-Conditional	None	49	49	0350	N/A	50
NetLibMerge	NETMERGE	Merge	None	49	49	0350	948	50
Overlay	OVERLAY	Replace	None	49	49	0350	N/A	50
PQDMerge	PQDMERGE	Merge	None	49	49	0350	856,948	50
Recon Conditional	RECONCON	Add-Conditional	None	49	49	010A, 020N,  022A, 0350, ISB3	N/A	80/60/60/100
SerSolMerge	SERMERGE	Merge	None	49	49	BBID	245,948	50

---

Profile definitions and uses:

Acq Conditional

Module: Acquisitions

Function: This profile compares the bib record the operator is trying to import with a bib in the existing database against the following fields:

010A (LCCN)

019A (OCLC Number : Cancelled)

020A (ISBN)

020Z (ISBN : Cancelled/Invalid)

022A (ISSN)

022Z (ISSN : Cancelled)

035A (System Number)

ISB3 (ISBN-13s will match ISBN-10s)

While importing records to add to a purchase order in Acquisitions, the following will happen:

If any of these fields in an imported record exactly matches any of the same fields on an existing record, the operator will receive a message that the record was not added because a duplicate exists, and will be offered the option of linking the line item being created to the existing bib.

Notes: Records detected as duplicates should not be linked to purchase orders. The operator should instead leave these records in the Import file and import them again in the Cataloging module, where they can be compared to the record(s) detected as (a) duplicate(s). After the operator has determined whether the imported record actually matches items in the database and imported the records as appropriate in Cataloging, s/he can return to Acquisitions and add the items to the purchase order being created using the "Bib Search" function.

Acq Import Conditional is the default profile in the Acquisitions module, and should only be used by operators in that module. The profile is selected as a default in System Administration rather than on individual workstations.

Back to Top

---

BIB Replace

Module: Bulk Import

Function: This profile is used to reload records extracted from Voyager for batch maintenance purposes. Matches on:

Notes: Used only with Bulk Import. Target records are extracted from Voyager, pre-processed, then reloaded.

---

Import Conditional

Module: Cataloging

Function: This profile compares the bib record the operator is trying to import with a bib in the existing database against the following fields:

010A (LCCN)

019A (OCLC Number : Cancelled)

020A (ISBN)

020Z (ISBN : Cancelled/Invalid)

022A (ISSN)

022Z ISSN : Cancelled

0350 (System Number)

2450 (Title Statement)

ISB3 (ISBN-13s will match ISBN-10s)

With Import Conditional as the default profile in the Cataloging module, the following will happen:

If any of these fields exactly matches the corresponding fields in an existing record, the system will block the import. The Bibliographic Dedupe Detection window will open, and the existing bib will be highlighted in that window. The operator will have the following options: backing out of the import attempt, overlaying the record, or merging the record (see Overlay and Merge 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.]

Notes: Import Conditional should be the default profile for all operators in Cataloging, and will be used for the vast majority of operator-initiated imports. This profile is designed to serve two purposes: to act as a limited safeguard against duplicate record creation, and to permit operators to match records for targeted overlay. To minimize both interference with the workflow and the impact on system performance, the profile relies primarily on standard numbers for its comparisons. Not every duplicate or potential duplicate will be detected. In addition, some records that are not duplicates may be detected as such when they match the 245 exactly. This profile is not a substitute for careful searching of the database. Operators cannot rely on the profile to exclude all duplicate records. Operators will also need to examine records detected as duplicates carefully to determine whether they do in fact match exactly.

In the Cataloging module, this profile is selected under Options--General, and needs to be done on a client-by-client basis.

Back to Top

---

Import Unconditional

Module: Cataloging

Function: This profile allows an operator in the Cataloging module to add a record without any duplicate checking. Import Unconditional could be useful when the operator is aware that a match may be encountered, but wishes to add the record anyway. An example might be adding a record for an electronic version of a serial when a print version is already in the database.

Notes: Import Unconditional is not designed to be used as a default profile setting. The field definition given in the table above is intended primarily as a placeholder in the Voyager System Administration module, where some value has to be added for the profile to exist. If an operator does use Import Unconditional as the default profile setting, all records being imported will be saved to the database without duplicate detection of any kind.

Back to Top

---

CJK Script Merge

Module: Bulk Import

Function: This profile is used for batch import of our CJK records from RLIN. Matches on:

0350 (RLIN System Number)

Notes: Used only with Bulk Import.

---

LC Replace

Module: Bulk Import

Function: This profile is used in loading updates to the LC Resource File. It compares LCCNs of incoming BIB records with those of existing records, overlaying updates to existing records and loading non-matches as new. Matches on:

010A (LCCN)

Notes: Used to load records in the Resource Database (RD) only.

---

MARCadiaMerge

Module: Bulk Import

Function: This profile is used to reload MARCadia upgrades of our In Process and CIP-level records into the production database.

Notes: Vendor retains 035, 950, 955 from exported records. USED FOR BULK IMPORT ONLY.

Back to Top

---

Marcive Merge Profiles

Module: Bulk Import

Function: These profiles are used load new and updated Marcive records for government documents.

Notes: Non-matches are loaded as new. USED FOR BULK IMPORT ONLY.

Back to Top

---

Merge

Module: Cataloging

Function: With Import Conditional as the default import/replace profile, Merge is one of the options available to the operator upon detection of a duplicate record. Merge can be used to retain certain information on an existing record (e.g., fuller contents notes for a multipart monograph, important locally-defined fields), while overlaying all other fields.

Notes: If the record being imported contains any of the defined merge fields, those fields will be retained in the merged record, not overlaid; the information retained from the target record will be added to the information in the incoming record. For example, if both the incoming record and the target record have a 505 field, and the operator chooses to merge the records, both 505s will appear on the final record. The record will need to be edited appropriately after the merge is complete.

Merge is not designed to be used as a default profile setting. The field definition given in the table above is intended primarily as a placeholder in the Voyager System Administration module, where some value has to be added for the profile to exist. If an operator does use Merge as the default profile setting, only records that match exactly on the 035 field will overlay existing items, and will do so without Dup Detection. If none of the fields listed above is on the existing record, Merge will function exactly like Overlay.

Back to Top

---

MIT Conditional

Module: Bulk Import

Function: This profile is used when batch loading MIT CogNet records. It compares the 035 field of incoming records with those of existing records, discarding matches and loading non-matches as new.

Notes: USED FOR BULK IMPORT ONLY

---

NetLibConditional and NetLibMerge

Module: Bulk Import

Function: These profiles are used in loading new and updated netLibrary records into the production database.

NetLibConditional compares 035 fields in incoming records with those of existing records, discarding matches, and loading non-matches as new.

NetLibMerge compares 035 fields in incoming BIB records with those of existing records, merging updates to matching existing records, and loading non-matches as new.

Merge fields:

Notes: USED FOR BULK IMPORT ONLY

Back to Top

---

Overlay

Module: Cataloging

Function: With Import Conditional as the default import/replace profile, Overlay will be one of the operator options upon detection of a duplicate record. Overlay can be used to overlay (or replace) an incomplete or lower quality bib record with a complete or superior one.

Notes: Overlay is not designed to be used as a default profile setting. The field definition given in the table above is intended primarily as a placeholder in the Voyager System Administration module, where some value has to be added for the profile to exist. If an operator does use Overlay as the default profile setting, only records that match exactly on the 035 field will overlay existing items, and will do so without Dup Detection.

Overlay is available only in the Cataloging module. Acquisitions staff who need to overlay a bib record would need to do so in Cataloging.

---

ProQuest Merge

Module: Bulk Import

Function: This profile is used for batch import of our ProQuest update records. ProQuest Merge matches on:

035 (MiAaPQ)

Notes: Used only with Bulk Import.

---

Recon Conditional

Module: Bulk Import

Function: This profile is used when importing recon records from OCLC. It compares the 010, 020, 022, and/or 035 of incoming records with those of existing records, discarding matches and loading non-matches as new.

Notes: USED FOR BULK IMPORT ONLY

---

Serial Solutions Merge

Module: Bulk Import

Function: This profile is used for batch import of our Serial Solutions update records. Serial Solutions Merge matches on:

Notes: Used only with Bulk Import.

Back to Top