You can import data from iBase databases, other databases, excel spreadsheets, or text files. Before you can import any data, you define how the source data is to be interpreted during the import in an import specification. You can run the import specifications singly or in a batch (if you first set up an import batch specification).
Before you create an import specification, compare the data that you would like to import with the database structure to determine the item types to import. In addition, determine the fields that are mandatory, and the fields that can be used as identifiers (used to decide whether data matches records in the database).
Validating and protecting the data
During the import, you can check that values imported into Selected from Code List type fields are valid; any invalid values are reported as errors during the import.
You can protect existing data by turning on the Do not update existing field values with blank values checkbox. This option prevents existing data from being overwritten by blank values in the source data.
Manipulating the data
- Copy a value to assign it to more than one field.
- Merge two or more values to assign them to a single field.
- Split a value to assign parts to several fields.
- Update specified values with new ones (for example where the source data uses a different code list) by creating a substitution file.
- Trim unwanted space from the start or end of a source field.
Recording the results of the import
You can record the results of the import by saving new and modified records in a set.
If required, you can log the numbers of new and modified records to a file.
You can save the errors that might occur during the import to a file. You can then fix the problems with the source data by editing the error file, and reimport the remainder of the data by using the error file as the source for the import.
Bulk imports and importing XML data
A bulk import allows significantly faster importing and importing from XML files. It is also useful for importing large quantities of data without user intervention. System administrators can set up a bulk import, that uses an import specification, although there are a few minor differences between a standard and a bulk import.
After importing large numbers of records, you might want to compact your database.