Insight contains five main data table types

1. Server Settings – contain settings for the server instance as opposed to the collection, like Media File Locations (SPS).

1. Catalog Template Settings – contain definitions for each of the catalog templates, including schema, field, and table properties.

1. Collection Settings – contain specific settings for collections such as background images, names, descriptions, etc.

1. Data Tables – contain the data for each collection once imported/indexed into Insight.

1. Indexer Tables – (optional) if used, data is drawn from the source tables using the indexer, and restructured for storage in the Insight Data Tables.

Figure 32: Basic Diagram of the Insight Table Structure

Indexer & Source Tables

In pre-5.x versions of Insight, there was a dependency on a set of source data tables to provide content for Insight. These source data tables, in the form of a relational database schema, were mapped and defined as a Catalog Template using Fields, Record Types, Record Relationships and Joins. The joins represent the relationships between the source data tables and enable the import of data into the Insight Data Tables via the Insight Indexer. The Record Types, Record Relationships, and Fields defined the data schema within Insight.
The basic indexing process was as follows:

1. Administrators would create the source data tables (or use those packaged with the VRA) within the Administrator Tools.
2. Administrators would import data into the source data tables.
3. Administrators would then run the Insight Indexer, which moves data from the source data tables into the Insight Indexer Tables (ITT Tables above).
4. Once the Indexing process was complete, the Indexer moves data from the Insight Indexer Tables into the Insight Data Tables.

Once this process was complete, the data imported using the indexer would be available within Insight.

Inscribe, Insight Studio, and the Indexer

Insight 5.x removes the requirement of source data tables now that Insight Studio provides data import tools to easily move content into any Insight Collection. The optional removal of data tables provides added flexibility as well as simpler management and collection creation for administrators. Both the source-table write-back and standard indexing methods are still supported for collections in 5.x, but are alternate configurations. When Catalog Templates are created in Insight Studio, table-based joins are optional. In place of the Indexer, Inscribe provides a method to add new records or make minor adjustments. Insight Studio enables bulk-import of data using the Data Import Module.
The data import process is as follows:

1. Catalogers add data via Inscribe, or collection administrators add data via Insight Studio.

1. Data is processed in the Collection Manager and written to the Insight Data Tables.