Contributing Records to the INN-Reach Catalog
Whenever you create, modify, or delete records in your local catalog, your Local Server automatically queues the updates to the local INN-Reach record-loading queue. INN-Reach reviews the queued updates and determines whether or not to load those records to the INN-Reach Catalog based on your local contribution profile.
Your contribution profile controls which records your system contributes to the INN-Reach Catalog, which fields in those records it contributes, and whether those records or fields display in the central WebPAC.
You can configure how INN-Reach contributes the following:
- Specific bibliographic, item, checkin, or order records
- Bibliographic records based on the presence of specific MARC-tagged fields
- Bibliographic records based on the owning agency
- Bibliographic records based on cataloging status
- Enhanced local record data
- MARC 001 (Control Number) fields in bibliographic records
- MARC 583 (Action Note) fields in local records
- URL fields stored in local bibliographic, item, checkin, or order records
Contributing Specific Bibliographic, Item, Checkin, and Order Records
You can control the contribution and display of a bibliographic record (with all its attached records) or an individual item, order, or checkin record by editing the contribution code in the record.
Your Local Server specifies which fixed-length field is used to control contribution for each record type. The fixed-length fields that can be used for contribution codes are described in the table below. The default field for each record type is shown in bold.
| Field | Records Affected |
|---|---|
| BCODE1, BCODE2, BCODE3 | Bibliographic record and all attached records |
| ICODE2 | Item records |
| CODE1, CODE2, CODE3, CODE4 | Order records |
| SCODE1, SCODE2, SCODE3, SCODE4 | Checkin records |
One Contribution Control Field per Record Type
You can use only one fixed-length field to designate contribution for each record type. For example, you cannot use both BCODE1 and BCODE2 for contribution control.
The values in these fixed-length fields specify whether the system:
- Contributes the record, but suppresses its display.
The system stores the record in the INN-Reachh Catalog, but does not display it in WebPAC on the INN-Reach Central Server. - Does not contribute the record.
The records are not contributed to the INN-Reach Catalog, that is, those records are not stored in the INN-Reach Catalog and remain available for local use only. For example, your library might use this type of suppression for professors' personal copies of items that have been placed on course reserve.
You can use the following standard codes to produce the following system actions:
| Code | Contribute to INN-Reach Catalog? |
Display in central WebPAC? |
Display in local catalog? |
|---|---|---|---|
| - | Yes | Yes | Yes |
| l | Yes | No | Yes |
| n | Yes | No | (as configured) |
| s | No | No | (as configured) |
| z | No | No | Yes |
Using the 'n' or 's' Code to Control Local Display
To use the 'n' or 's' code to control the display of records in your local catalog, your Local Server must be set up to recognize the code. If you want to use either of these codes to control the display of records in your local catalog, ask your Local Server Coordinator to contact Innovative.
Mapping BCODE Values
If your Local Server uses additional or different suppression codes in BCODE1, BCODE2, or BCODE3, or if the standard codes conflict with your current BCODE values, INN-Reach can automatically map your Local Server's codes to the standard INN-Reach actions as records are transferred to the INN-Reach Catalog. If your Local Server requires BCODE mapping, ask your Local Server Coordinator to contact Innovative.
Contributing Bibliographic Records Based on Specific MARC-tagged Fields
If your Local Server has the Customized INN-Reach Record Contribution feature enabled, you can contribute bibliographic records to the INN-Reach Catalog based on the presence of specific MARC-tagged fields in the records. This feature enables you to override the standard contribution codes in the bibliographic records without editing the individual records. For example:
- If your site wants to contribute only serials to the central catalog (for example, for participation in ArticleReach), your Local Server can be configured to contribute only those bibliographic records that contain a MARC 022 (ISSN) field.
- If your site wants to prevent the contribution of briefly catalogued records, your Local Server can be configured to contribute only those records that contain at least one instance of the following fields: MARC 008 (Fixed-Length Data Elements), MARC 245 (Title), MARC 260 (Imprint), and MARC 300 (Physical Description). Note that a record must contain ALL of the specified fields in order to be contributed.
If you want to contribute records that do not have the MARC-tagged field(s) you have specified, you can use a "force" code in the fixed-length field that your Local Server uses to control bibliographic record contribution (for example, BCODE3). Your Local Server defines the force code when this feature is enabled. The force code must be one character and unique in the contribution code field in which it is used.
If your Local Server contributes to more than one INN-Reach Central Server, the Customized INN-Reach Record Contribution feature can be configured separately for each INN-Reach Central Server to which you contribute. You can specify different MARC-tagged fields and a different force code for each INN-Reach Central Server.
Contributing Bibliographic Records Based on Owning Agency
If your Local Server has the Agency-based INN-Reach Record Contribution feature enabled, you can specify which agencies on your Local Server contribute records to the INN-Reach Catalog. INN-Reach contributes only those bibliographic records that contain a LOCATION fixed-length field value that maps to a contributing agency.
If your Local Server contributes to more than one INN-Reach Catalog, you can specify a different list of agencies to contribute to each Central Server. For example, if your Local Server hosts agencies A, B, and C, and it contributes records to INN-Reach Catalog Y and INN-Reach Catalog Z, you can specify that agencies A and B contribute records to catalog Y only, while agency C contributes to catalog Z only.
Contributing Bibliographic Records Based on Cataloging Status
Depending on your library's cataloging practices, your local catalog can contain bibliographic records that are in the process of being fully cataloged. These records might not immediately meet the standards of the INN-Reach Catalog to which they are to be contributed. Rather than suppressing individual records manually, your library can prevent their contribution based on the following attributes:
- Blank CAT DATE field
- Your Local Server can be configured to contribute only those records that contain data in the CAT DATE field.
- Capitalized TITLE field
- If your local catalog contains records obtained directly from a cataloging vendor, and the vendor delivers bibliographic records with TITLE data entirely in capital letters, your system can be configured to prevent records with that attribute from contributing to the INN-Reach Catalog.
To prevent contribution, all text in subfield $a of the TITLE field must be capitalized. For example, a bibliographic record with the following TITLE field would not be contributed:245|aMARE'S WAR
A bibliographic record with the following TITLE field would be contributed:245|aMare's WAR
Contributing Enhanced Local Record Data
Your Local Server can be configured to enhance data from local bibliographic records prior to transmitting it to the INN-Reach Catalog. The source data in the local bibliographic record remains unchanged, but INN-Reach contributes a modified version of the data.
These features include:
- Enhanced Encoding Contribution
- The Enhanced Encoding Contribution feature enables your Local Server to assign automatically an Encoding Level (byte 17 of the MARC Leader field) based on the presence of specific fields in the bibliographic records. This feature enables the system to assign a higher encoding level to records that are more completely catalogued at your Local Server. The INN-Reach Catalog uses this encoding level to determine a master record.
- Filtering Repeatable Fields
- The Filtering Repeatable Fields feature enables your Local Server to contribute only the first instance of specified repeatable MARC-tagged fields from bibliographic records. For example, if bibliographic records in your local catalog contain multiple MARC 050 (Call Number) fields, your Local Server can be configured to filter out all but the first MARC 050 field in the version of the record it transmits to the INN-Reach Catalog.
Contributing MARC 001 Fields in Bibliographic Records
- The MARC 001 (Control Number) field in the bibliographic record is often used as a Primary Match Field on the INN-Reach Central Server. As a result, contributed bibliographic records must always contain MARC 001 fields. If a local bibliographic record does not contain a MARC 001 field, the Local Server automatically generates MARC 001 field data for the record before contributing it.
- If there are multiple MARC 001 fields in a local bibliographic record, your Local Server contributes only the first MARC 001 field in the record.
According to MARC standards, the MARC 001 field is non-repeatable. Consequently, when a bibliographic record with multiple occurrences of the 001 field is created or updated at a site, the Local Server drops all but the first 001 field from the record before sending it to the INN-Reach Central Server.
For these records, the system logs a MULTIPLE 001 FIELDS message with the bibliographic record number to the local system message file. For information on viewing this file, see Administering System Files. - The Local Server automatically strips spaces and leading zeroes in MARC 001 fields prior to contribution.
- To optimize matching on the MARC 001 field in the INN-Reach Catalog, Innovative can configure your Local Server to strip prefix characters from MARC 001 data before contribution. For example, if MARC 001 data on your Local Server is prefixed with "ocm", the system can strip those characters from the MARC 001 data contributed to the INN-Reach Catalog. The records you contribute can then be matched to existing records that store MARC 001 data without the specified prefix.
Contributing MARC 583 (Action Note) Fields in Local Records
If the INN-Reach Shared Print Management feature is enabled for your INN-Reach System, Innovative can configure your Local Server to contribute MARC 583 fields that are stored locally in bibliographic and/or item records.
Contributing URL Fields in Local Records
Innovative can configure your Local Server to contribute the following types of local URL fields to the INN-Reach Catalog:
- MARC 856-tagged URL fields in local bibliographic records
- Alternate URL fields in local bibliographic records (if your INN-Reach System has acquired the "INN-Reach URLs for Locally Held Resources" product)
- URL fields stored in local item, order, or checkin records. Note the system only contributes the first instance of a URL field in these records; additional URL fields in the same record are not contributed.
For information on how the INN-Reach Catalog stores and displays the contributed URL fields, see Storing URL Fields in the INN-Reach Catalog.
If your local bibliographic records contain MARC 856-tagged fields that are intended for local use only, you can contribute the records but prevent the URL fields from being stored in the INN-Reach Catalog based on the presence of a specific phrase in the fields. For more information, see Storing Selected MARC 856 Fields.