-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathreference-data-alignment.json
More file actions
48 lines (48 loc) · 1.78 KB
/
reference-data-alignment.json
File metadata and controls
48 lines (48 loc) · 1.78 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
{
"id": "reference-data-alignment",
"name": "Reference data alignment",
"description": "Map external ERP field names to a canonical Customer record type, validate, then persist.",
"instructions": "1. Install and open the playbook view for the Customer record type and connector ingest.\n2. POST JSON using source-system keys (cust_id, company, contact_email) — the Field Mapper renames them to canonical fields.\n3. Failed validations route to the landing zone.\n4. Use Graph View after RDF sync to see the Customer class in your ontology.\n\n**MCP (playbook id: `reference-data-alignment`):** health_check → anythinggraph://schema-summary or get_entity → create_entity_row. Bulk ingest via playbook connector webhook after install.",
"entities": [
{
"name": "ref_customer",
"display_name": "Customer",
"fields": [
{
"field_name": "customer_id",
"field_type": "TEXT",
"is_required": true,
"is_identifier": true,
"description": "Canonical customer identifier",
"example": "C-10042"
},
{
"field_name": "legal_name",
"field_type": "TEXT",
"is_required": true,
"description": "Legal company name",
"example": "Northwind Traders Ltd"
},
{
"field_name": "contact_email",
"field_type": "TEXT",
"description": "Primary contact email",
"example": "billing@northwind.example"
}
]
}
],
"example_data": {
"rows": [
{
"entity_name": "ref_customer",
"values": {
"customer_id": "C-10042",
"legal_name": "Northwind Traders Ltd",
"contact_email": "billing@northwind.example"
}
}
]
},
"category": "integrate_data"
}