Data Mapping

​

Overview

Data mapping defines how raw fields from your external data sources are transformed into entities and relationships in the knowledge graph. Mappings tell Experio how to interpret structured data (CSV, Excel, databases) and create the corresponding graph nodes and edges. Navigate to Admin > Data Sources > Data Mapping.

​

Viewing Mappings

The data mapping page shows a table of all configured mappings with server-side pagination. Each entry displays the mapping name, configuration details, and compatibility status against the current ontology revision. Filter to invalid or stale mappings when you need to clean up after an ontology change. See Ontology Compatibility.

​

Creating a Mapping

Click Create New Mapping to open the mapping editor. The mapping editor provides two modes:

​

Form Builder

A step-by-step form interface for defining:

1. Source Fields — Select which fields from your data source to use
2. Node Mappings — Define how source fields map to entity types in your ontology
3. Relationship Mappings — Define how relationships between entities are derived from the data

​

Visual Canvas

An interactive drag-and-drop canvas (powered by React Flow) for visually designing mappings:

• Drag source fields onto the canvas
• Connect fields to entity types and properties
• Draw relationship lines between entities
• Zoom and pan to navigate complex mappings

​

Mapping Components

​

Source Fields

Define the raw fields available from your data source. Each field has:

• Field name — The column or property name in the source data
• Data type — String, number, date, etc.

​

Node Mappings

Map source fields to entity properties: Each mapped property displays its ontology type (text, number, date, boolean, list, enum). You do not configure per-field transforms in the mapping UI — types come from the ontology definition for that entity.

​

Property types and graph writes

At ingestion time, Experio coerces mapped values to the ontology type before writing to the graph: Structured and unstructured ingestion share the same coercion path. Ensure source columns are parseable for the target type (for example, ISO or common date formats for date fields).

​

Relationship Mappings

Define how entities are connected:

​

Editing and Deleting

• Click any mapping row to edit its configuration
• Use the delete action to remove a mapping

The mapping editor includes a compatibility panel. If node or relationship mappings point at ontology elements that no longer exist, the mapping is invalid until you update it and Re-validate. After a rename that already looks correct, Mark as reviewed clears stale status.