Determining the Master Record
To enable the Enhanced Master Record Determination feature for your INN-Reach System, ask your Central System Administrator to contact Innovative.
To determine if a bibliographic record is the master record in the INN-Reach Catalog, the INN-Reach Central Server does the following:
- Determines whether the bibliographic record has been manually claimed as a master record using the Master Owner feature:
- If one of the matched records—either the incoming bibliographic record or the existing central bibliographic record—has been manually claimed as a master record, that record becomes (or remains) the master record in the INN-Reach Catalog.
- If neither or both of the matched records have been manually claimed as a master record, the system continues to the next step.
- Evaluates the records according to specific criteria.
By default, the INN-Reach Central Server evaluates ownership using the Encoding Level (MARC Leader byte 17) and the contributing site's Library Load Priority Level.
If your INN-Reach System has had the Enhanced Master Record Determination feature enabled, the INN-Reach Central Server can be configured to evaluate ownership using any combination of the following criteria:
Configuring Ownership Criteria by Bibliographic Level
Your INN-Reach System can be configured to apply different ownership criteria based on the Bibliographic Level (Leader byte 7) value. For example, the system can use a different set of criteria to evaluate ownership for serials (Leader byte 7 equal to "s") than it does for monographs (Leader byte 7 equal to "m").
Once INN-Reach determines ownership of the master record, it modifies the affected records as appropriate. For more information, see Modifying an INN-Reach Catalog Record.
Existence of a Specific MARC-tagged Field
The system assigns ownership to the record that contains a specified field or subfield. For example, your INN-Reach System can assign ownership to those records that contain a MARC 008 (Fixed-Length Data Elements) field. When the system evaluates the following records:
Rec 1 y008 001215s2000 nyu b 001 0 eng nam4a
Rec 2
it assigns ownership to Rec 1, because it contains a MARC 008 field, and Rec 2 does not.
If neither or both records contain the specified field, the system cannot assign ownership based on this test.
Length of a Specific MARC-tagged Field
The system assigns ownership based on the length of a specified field or subfield. The system can conduct two types of length evaluations:
- Specific length. The system evaluates whether the specified field/subfield is equal to or greater than a specific number of characters. If one record contains a field that equals or exceeds the specified length, the system assigns ownership to that record. For example, your INN-Reach System can assign ownership to those records that contain a MARC 300$a subfield of 15 characters or greater. When the system evaluates the following records:Rec 1 r300 |a4 videodiscs (ca. 611 min.) :|bsd., col. ;|c4 3/4 in
Rec 2 r300 |a4 videodiscs
it assigns ownership to Rec 1, because it contains more than 15 characters, while Rec 2 does not. - Relative length. The system evaluates whether the specified field/subfield in one record is longer than the specified field/subfield in the other record. For example, your INN-Reach System can assign ownership to those records that contain the MARC 300$a subfield with the most data. When the system evaluates the following records:Rec 1 r300 |a4 videodiscs (ca. 611 min.) :|bsd., col. ;|c4 3/4 in
Rec 2 r300 |a4 videodiscs
it assigns ownership to Rec 1, because its MARC 300$a subfield is longer than the MARC 300$a subfield in Rec2.
Note:
- If one of the matched records has the specified field/subfield and the other record does not, the system evaluates the record without the field as having a zero-length field.
- If both matched records contain the specified field/subfield of equal length, the system cannot assign ownership using this criteria.
- Before counting the characters in the field/subfield, the system normalizes the data. Your INN-Reach system chooses the normalization rule used during configuration of the ownership algorithm.
Occurrences of a Specific MARC-tagged Field
The system assigns ownership to the record that contains the greater number of specified repeatable fields. For example, your INN-Reach System can assign ownership to those records that contain the greater number of MARC 6XX (Subject Access) fields. When the system evaluates the following records:
Rec1 d60010|aChiang, Kai-shek,|d1887-1975.
d60010|aChiang, May-ling Soong,|d1897-2003
Rec2 60010|aChiang, Kai-shek,|d1887-1975.
it assigns ownership to Rec1 because it contains two MARC 600 (Subject Added Entry - Personal Name) fields, and Rec 2 contains only one.
If the matched records contain an equal number of the specified fields, the system cannot determine ownership based on this criteria.
Specific Text in a MARC-tagged Field
The system assigns ownership to the record that contains specific text in a specific MARC-tagged field.
For example, your INN-Reach System can assign ownership to those records that were obtained from a specific cataloging source (that is, records with a MARC 40$a subfield that contains the MARC organization code of specific cataloging source, in this case, "DLC"). When the system evaluates the following records:
Rec1 i040 |aDLC|cDLC|dDLC
Rec2 i040 |aSTF|cSTF
it assigns ownership to Rec1 because it contains a MARC 040$a value of "DLC", and Rec2 does not.
If neither or both of the records contain fields containing the specified text, the system cannot determine ownership using this criteria.
Descriptive Cataloging (Leader Byte 18)
The Descriptive Cataloging element (byte 18) of the MARC Leader field specifies the cataloging standard used to create the record. Valid values for this element include:
| Value | Cataloging Standard |
|---|---|
| a | AACR2 |
| i | ISBD |
| <empty> | non-ISBD |
| u | unknown |
The system can assign ownership to the record that contains a specific value in this element. For example, the system can assign ownership to those records that contain a Leader byte 18 value of "a".
Alternately, the system can compare this element in both of the matched records and assign ownership based on a hierarchy of valid values. For example, your INN-Reach system might prefer records cataloged using the AACR2 standard over records cataloged using the ISBD standard. When the system evaluates an incoming record has a Leader byte 18 value of "a" and an existing central bibliographic record with a Leader byte 18 value of "i", it assigns ownership to the incoming record.
Encoding Level
Viewing the Encoding Level of a Bibliographic Record
To determine the Encoding Level of a record, view the Leader field in the local bibliographic record.
The system assigns ownership to the record with the higher Encoding Level. For example, if the incoming record has a higher Encoding Level than the existing record, the system assigns ownership to the incoming record.
The Encoding Level is determined based on the following:
- Byte 17 of the MARC Leader field, if present.
- Byte 48 of the MARC 008 field, if no Leader field is present.
- The hard-coded value 'z' if Byte 48 is absent from the MARC 008 field. (This value is equivalent to a 'z' value in Byte 17, defined in the MARC standards as "not applicable".)
INN-Reach groups Byte 17 values for evaluation, with some levels considered equal. For example, in the table below, Encoding Levels 5 (partial level) and 7 (minimal level) have equal load value. The Encoding Levels and Encoding Groups described below encompass both codes found in US MARC standards and codes defined by OCLC. The list begins with the highest group first, that is, group 10.
| Encoding Group | Encoding Level | Meaning |
|---|---|---|
| 10 | (blank) | Full Level |
| 9 | I | Full Level input by an OCLC library |
| 4 | Core level | |
| 8 | 1 | Full Level, material not examined |
| 7 | L | Non-LC & non-NLM loaded from tape |
| 6 | K | Less than full input by an OCLC library |
| J | Record deleted by LC from MARC file | |
| 2 | Less than full level | |
| M | Less than full level, tape loaded | |
| 5 | 8 | CIP prepublication data |
| 4 | 5 | Partial level |
| 7 | Minimal level | |
| 3 | E | System-identified error in LC MARC record |
| W | Warning, possible error in LC MARC record | |
| 3 | Abbreviated level | |
| 2 | U | Unknown |
| Z | Not applicable |
Library Load Priority Level
The system assigns ownership based on the owning site's Priority Level in the Library Load Priority Table. The record contributed by the site with the higher Priority Level becomes the master record. If the Priority Levels of the sites that contributed the incoming and existing records are the same, the system retains as the master record the record that was contributed first to the INN-Reach Catalog.
Library of Congress Call Number (MARC 050)
Depending on local cataloging practices, bibliographic records can be contributed to the INN-Reach Catalog with Library of Congress Call Number (MARC 050) fields that contain local data that is not relevant in the INN-Reach Catalog. For example:
| Local data with call number | c050 |aSCIENCE GH234.5 V234 |
| Valid call number | c050 |aGH234.5 V234 |
A valid call number is defined as a MARC 050$a value that contains no more than three contiguous alphabetic characters. (In the example above, the valid call number contains only two contiguous alphabetic characters, "GH".) In order to retain the most relevant call number data in the INN-Reach Catalog, INN-Reach can be configured to assign ownership to the record that contains a MARC 050 field that meets this validity criteria.
This validation test can be combined with an existence test on the MARC 050 field, so that the system can assign ownership in cases where one of the matched records contains a MARC 050 field, but the other does not. In such cases, the system assigns ownership to the record that contains the MARC 050 field.
In addition, the system can be configured to assign ownership in cases where the MARC 050$a data in both records passes or fails the validity test (that is, when both records contain valid MARC 050$a values or both records contain invalid MARC 050$a values). In such cases, the system can be configured to assign ownership to the record that contains a Dewey Decimal Classification Number (MARC 082) field.