Load Tables

After records have been imported to the Innovative server, they must be translated from their existing format into the storage format used by your database (that is, "preprocessed"). In accordance with your library's specifications, Innovative sets up "load tables" that are used to map the existing format to the storage format.

Load tables can also contain commands to be executed as records are loaded into the Innovative database. For example, commands can overlay fields in existing records with data from incoming records or create attached records using data in specified fields of incoming records.

Load tables are used during the load to:

• specify which fields and subfields in the incoming record are retained when the record is loaded in the Innovative database
• map fields and subfields in the incoming record to the fields and subfields that are loaded into the Innovative database
• map MARC tags in the incoming record to MARC tags that are loaded into the Innovative database
• map MARC tags in the incoming record to field group tags that are loaded into the Innovative database
• specify whether to map BIB LEVEL and/or MAT TYPE from the leader of the MARC record
• specify if CAT DATE should be inserted in the record during the load, and if so, whether it is today's date or a date from a template
• if the incoming record contains no data for one or more fixed-length fields, specify the default values to insert into the record during load
• determine the action the system takes if the record you are loading matches a record already stored in your database (i.e., create a new record, overlay fields in the existing record with fields from the incoming record, or reject the incoming record)
• specify fields in existing records that are protected from overlay
• specify the types of attached records to create during the load

To request changes in a load table or create a new load table, contact Innovative. Contact Innovative to change the default load table used for Z39.50 transfer.

You can view your library's load tables in the Admin Corner.

Common examples of load tables are m2btab.b, m2btab.order, m2btab.bta, m2btab.anam, m2btab.asub, m2btab.batch, and m2btab.p.

A trigger in the load table determines which field(s) in incoming records contain the values that are interpreted as "holding symbols." Holding symbols are used to:

• insert a branch code into the bibliographic record LOCATION fixed-length field of the stored record
• specify which 6XX fields in incoming records are converted to the stored record format
• specify a prioritized list of fields in imported bibliographic records that can contain the call number for the the stored record

You can use holding symbols for records that cannot be edited before they are imported by entering in the holding symbol file some value that holds true for all records (for example, 245 subfield 'a' exists). You can edit the holding symbol file with Advanced System Access & Administration .