Step by step process - sinyphilip24/Fabric-IQ-Ontology GitHub Wiki

  1. Ingested batch data, telemetry data and report into the lakehouse
  1. Create entity types and data bindings First, create entity types. Entity types represent types of objects in a business. This step has three entity types: Store, Products, and SaleEvent. After you create the entity types, create their properties by binding source data columns in the IQ_Lakehouse lakehouse tables.
  1. Observe the sections of the configuration page: Entity type key: Identifies the field (or fields) that can be used to uniquely identify each record of ingested data.

Binding selection: Identifies the source table that holds the data for the binding.

Entity type key mapping: Identifies the column(s) in the source data table that map to the entity type key property. You can select string and integer columns from your source data as the entity type key. Together, the columns you select uniquely identify a record.

Properties: Lists the columns from the source data that will be represented as properties on the Store entity type. The Source column side populates automatically with the columns from the dimstore table, and the Property name side lists their corresponding property names on the Store entity type within ontology. For this tutorial, keep the default property names.

  1. You see the Configure page of the entity type details. This page surfaces important information about the entity type, including its properties and data bindings.

Created for Store, Products and sales event

  1. create relationship types between the entity types to represent contextual connections in your data.
  1. Configure the relationship
  1. Relationship is created
  1. Similarly create another relationship 'sold' from Salesevent to Product
  1. Enriching the ontology

Enriched the ontology using the telemetry data. This entity type adds more domain context and introduces properties for time series data, which reflects live operational information.

Note

For both static and time series data, you can create properties without binding data and bind data later, or create properties and bind data to them in a single step.

The properties are added to the Configure page, unbound to any data source.

10.2 Bind static data to properties.

10.3 Bind timeseries data to additional properties

10.4 Add relationship type

  1. Add Metadata and business rules
  1. Add Entity Metadata
  1. Creating ontology