Deletion views and columns

Deploying i2 Analyze automatically generates a set of deletion views in the IS_Public schema that is part of the Information Store. Using the views, you can browse the record data and write SQL queries that select records for deletion.

Use the IS_Public.Deletion_View_Lookup view to determine the deletion view names in your Information Store. You can also use the view to understand how the deletion views relate to the schema type IDs. The following table contains some examples.

Table 1. Extract from a sample Deletion_View_Lookup view
Schema type identifier	Display name	Deletion view name
ET2	Event	E_Event_DV
ET5	Person	E_Person_DV
ET8	Communications device	E_Communications_Device_DV
ET10	Account	E_Account_DV
LCO1	Communication	L_Communication_DV
LAS1	Associate	L_Associate_DV
LAC1	Access To	L_Access_To_DV

There is a deletion view for each record type. Each of these views has a suffix of _DV. Prefixes of E_ and L_ are used for entities and links. In IBM Data Studio or SQL Server Management Studio, you can expand a view to see its columns.

Any columns with a prefix of P_ contain values of properties that are defined in the i2 Analyze schema. The other columns contain metadata values that it might be useful to base rules on. Each view has columns for property values, which vary by item type, and columns for metadata values that are common to all records. The following table contains some examples of property columns.

Table 2. Sample extract of deletion views and properties from an IS_Public schema
Deletion view name	Column name	Sample value
E_Person_DV	p_unique_reference p_date_of_birth p_gender ...	P86539K 1932-10-14 Male ...
L_Access_To_DV	p_unique_reference p_type_of_use ...	ADC153 Account Holder ...

Metadata columns can be useful for creating deletion rule conditions. All deletion views have a common set of metadata columns as described in the following table.

Table 3. Metadata columns that are common across deletion views
Column name	Description
record_id	The record identifier that distinguishes the i2 Analyze record uniquely throughout the deployment
item_id	The item identifier that distinguishes i2 Analyze records of a particular type within the Information Store
last_update_time	The timestamp of the most recent i2 Analyze data ingestion
create_time	The timestamp that i2 Analyze assigned at the point of creation of the record
source_names	The names of the sources of the data
source_created	The timestamp from the external source for the creation of the data
source_last_updated	The timestamp from the external source for the last update of the data

Note:

In the Information Store, there is a one-to-one mapping between record identifiers and item identifiers. For more information about the identifiers that are used in i2 Analyze, see Identifiers in i2 Analyze records.
Records that are created through i2 Analyst's Notebook have a value of ANALYST in the source_names column and null values for source_created and source_last_updated.

Views that represent link types have a few extra metadata columns as described in the following table.

Table 4. Metadata columns that are specific to link records
Column name	Description
from_record_id, from_item_id	The identifiers of the record that constitutes the start of a link
to_record_id, to_item_id	The identifiers of the record that constitutes the end of a link
from_item_type_id	The identifier of the type of the record that constitutes the start of a link
to_item_type_id	The identifier of the type of the record that constitutes the end of a link

Each deletion view has a security dimension column, which contains the security dimension values for each record. For more information, see Security model. It can be useful to delete records based on their security dimension values.

Note: The deletion of data is not subject to restriction based on the i2 Analyze security dimension values, but you can filter data for deletion based on these values.