Creating an ingestion mapping file
The mappings in an ingestion mapping file define how rows in staging tables become i2 Analyze records in the Information Store during the ingestion process. Each mapping that you write describes how to construct the origin identifiers for data of a particular type, and specifies the security dimension values that apply to records.
Before you begin
About this task
The Information Store ingestion mechanism makes it possible for you to develop and extend your ingestion mappings over time. You can test your approach to ingestion by writing and using a single (entity type) mapping, and then adding more entity type and link type mappings later. You can put all your mappings in one file, or put each mapping in a separate file, or anything between those two extremes.
Procedure
If you populated the staging tables successfully, then writing ingestion mappings can be straightforward. Eventually, you need a mapping for each staging table that you created, but you can approach the problem one mapping at a time.
Example
The examples\data\law-enforcement-data-set-1 directory of the deployment toolkit contains an ingestion mapping file named mapping.xml. This file contains ingestion mappings for all the staging tables that the ingestion example creates. You can use mapping.xml as the basis for the ingestion mappings that you need for your data.