Ingestion resources The ingestion resources section contains information that is referenced elsewhere in the ingestion section. Understanding the architectureThe physical architecture of your i2 Analyze deployment both affects and is affected by how you acquire and transform external data for the Information Store. Depending on the architecture, you might need to perform more deployment tasks before you can run data ingestion commands.Information Store staging tablesAt your request, i2 Analyze generates an Information Store staging table that can contain data for i2 Analyze records of a single entity type or link type. To generate the staging table, it uses information from the i2 Analyze schema, which is the same starting point from which it generates the main data tables during deployment.Information Store property value rangesThe Information Store places limits on the ranges of values that properties can contain. Different logical types in the i2 Analyze schema imply different limits, which are not always the same as the restrictions on the underlying database. It is important to consider the limits when you prepare data for ingestion.Ingestion mapping filesAn ingestion mapping file is an XML document whose structure is validated during the ingestion process. Every time that you instruct the Information Store to ingest data, you specify both the mapping file to use, and the ingestion mapping within it. You can choose to put all your ingestion mappings in one file, or to spread them across several files.Origin identifiersThe role of a source identifier is to reference the data for a record reproducibly in its original source. The source identifiers that records receive during ingestion are unique within i2 Analyze, and they have a special name in this context. They are called origin identifiers.The ingestInformationStoreRecords taskThe parameters and usage of the ingestInformationStoreRecords depends on whether you are using the i2 Analyze deployment toolkit or the ETL toolkit.The previewDeleteProvenance and deleteProvenance tasksTo update the Information Store for deleted data in an external source, you update the Information Store by using staging tables and the deployment toolkit.Understanding ingestion reportsEvery attempt to add, update, or delete data in the Information Store through the deployment or ETL toolkit adds rows to the IS_Public.Ingestion_Deletion_Reports view. You can use the contents of this view to track the history of all such operations, and to examine the impact of a particular operation.Troubleshooting the ingestion processThe commands that you run during the ingestion process send information about their progress to the command line and a log file. If any command encounters errors or does not run to completion, you can read the output to help you to diagnose the problem.Parent topic: Information Store data ingestion
