Loading Records to the INN-Reach Catalog
All record loading to the INN-Reach Catalog is accomplished by moving records across the network from the Local Servers to the INN-Reach Central Server. The records are not loaded from tape, but are automatically transferred by INN-Reach. Once record contribution is activated, all additions or changes to records on the Local Server are automatically transmitted to the INN-Reach Catalog. Once INN-Reach record-loading is enabled, staff do not need to perform any extra procedures to load or update records from the Local Server to the INN-Reach Catalog.
Under certain circumstances, a Local Server might want to supplement automatic record-loading by manually loading records to the INN-Reach Catalog. For more information, see Sending Selected Records to the INN-Reach Catalog.
The updates sent to the INN-Reach Catalog include changes the Local Server makes to the local bibliographic, item, checkin, and order records, including changes made by item circulation. For example, as an item circulates on the Local Server and is checked out, the circulation status and due date are transmitted to the INN-Reach Catalog. The corresponding ITEM field in the institution record in the INN-Reach Central Server is modified to reflect this activity.
Most modifications you make to records in your local catalog trigger INN-Reach to queue the modified records for transmission to the INN-Reach Central Server. Specifically, records are queued when you modify the following fields:
Local Record Type |
Field Names |
---|---|
Bibliographic | Any field. |
Item | Any field that is part of the ITEM (i949) field in the institution record. |
Order | The fixed-length fields ACQ TYPE, LOCATION, RDATE, STATUS, and the field that the Local Server uses to specify central contribution (CODE1, CODE2, CODE3, or CODE4). |
Checkin | The fixed-length field LOCATION and the field that the Local Server uses to specify central contribution (SCODE1, SCODE2, SCODE3, or SCODE4), and the variable-length fields CALL #, LIB HAS, and IDENTITY. |
A modification of the contribution code for a record always causes the record to queue for transmission to the INN-Reach Central Server. For example, if you change the contribution code so that the record no longer contributes to the INN-Reach Catalog, the record is transmitted to the INN-Reach Central Server to be deleted from the INN-Reach Catalog.
The INN-Reach software on the Local Server notifies the INN-Reach Central Server when queued records are ready to be transmitted.
Increasing Record Loading Efficiency at High-volume Servers
If your Local Server generates a high volume of record updates, Innovative can enable features that optimize record loading throughput from your Local Server to the INN-Reach Central Server:
- Separate Record-loading and Circulation Queues
- Your Local Server can be configured to process record loading and circulation activity in separate queues.
- Enhanced Queue Processing
- Your Local Server can be configured to remove duplicate record updates before writing the updates to the link file.
- Prioritized Record Loading
- Record loading throughput to the INN-Reach Central Server can be prioritized by Local Server to assist in balancing incoming transmissions at the INN-Reach Central Server.
For more information or to see if these features would be beneficial for your Local Server, ask your Central System Administrator to contact Innovative.