►Data Exchange> Import Batch
The import file(s) should be unzipped and saved to a convenient directory locally. If the data is from several sources there may be several files in the zip archive. In this case a new import batch record will be needed for each file.
BC | Copy Barcode |
---|---|
IS |
ISxN |
INVIS | Invalid ISxN value |
RN | Record Number. Data in this tag imports to / exports from the Record Control Number field in OLIB. Sometimes referred to as “Import RCN” or just “RCN” . |
TNUPD | Title import record control number. Refers to the Title Number. It is used for imports where the incoming data is intended to supplement the existing records. For example, when there are additional copies. |
XC | Title control number |
OLSTF: Add Copies for matching records | This will match an existing title record and process only the copy data, adding the copy to the title (provided there is no clash with the barcode). If an incoming record does not match an existing title, nothing of the incoming record will be processed. |
---|---|
OLSTF: Add new; Ignore matching records | This option will only add new title and copy records. If the incoming record matches an existing title, nothing of the incoming record will be processed. |
OLSTF: Add new; Add Copies for matching record | This option will add new title and copy records, but will also add copies for matching records as per the first option above |
OLSTF: Add new: Replace matching records | |
OLSTF: Add new; Update matching records |
(Records can be updated / replaced / holdings added etc.)
The Import Settings sheet is for information only. The value in the Default column is what is set if the import file does not contain a value. The import settings can be changed in the Data Exchange> Import Settings domain, normally via OCLC Support.
A confirmation that the batch is scheduled for immediate load is displayed, click Ok.
There are several ways you can check the progress of a batch dataload.
It may become necessary to restart a dataload.
The same process is used for loading later batches, except that if they are for new trials or for the live conversion the existing data must be removed before the data is loaded. As this requires SQL*Plus access to run a script to clean out the database this process will either be carried out by OCLC over the remote access link or advice will be given to local technical support on how to remove the catalogue data. Care should be taken to retain reference data (e.g. loan terms and media types) and any configuration changes. Once the data has been removed (which can easily be established by running a wildcard% search in the Titles domain) then the OLSTF Titles import can be run again for the new data.