Schema Lineage
Connect schema fields to model properties in the data model, enabling developers to trace data from API contracts through schemas to model entities.
Schema lineage connects schema fields to properties in your data model. Each lineage entry maps a field to a specific entity and property in the model.neoarc file, creating a traceable chain from API contracts through schemas to the underlying data model.
How Schema Lineage Works
Lineage entries use sourceType: "graph" with a reference to the model file. Each entry identifies the target entity and property within the model.
{
"sourceType": "graph",
"graphFilePath": "model.neoarc",
"nodeName": "Customer",
"nodeId": "a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d",
"propertyName": "Email"
}The Lineage Chain
Lineage creates a three-layer traceability chain across your architecture documentation:
Multiple Lineage Entries
A single schema field can map to multiple model properties. This handles real-world data scenarios where a field draws from more than one source.
Adding Lineage in the Schema Editor
The lineage picker displays model entities and their properties, allowing you to select the target directly.
Lineage Indicators
In the Schema Editor, fields with lineage display an [L] indicator, making it straightforward to see which fields have documented model sources and which still need mapping.
Tracing from API to Model
To trace data from an API endpoint to its model source:
Lineage Overrides for Inheritance
When using schema inheritance, derived schemas often need different lineage mappings than the parent. Each derived schema can override the lineage for inherited fields to point to the correct model entity and property.