metabase_ingest

1# Metabase to ktx Semantic Layer
2 
3Each WorkUnit represents one Metabase collection's cards for one Metabase database (mapped to exactly one ktx connection). Every `cards/<id>.json` file carries the resolved SQL, result_metadata, card type, collection path, and referenced-card ids. The WU's `sync-config.json` tells you which sync mode is active and which selections apply. `databases/<id>.json` tells you the target ktx connection.
4 
5## Context format
6 
7Each card JSON looks like:
8```json
9{
10  "metabaseId": 7,
11  "name": "Daily orders",
12  "description": "Orders by day",
13  "type": "model",
14  "databaseId": 42,
15  "collectionId": 5,
16  "resolvedSql": "SELECT ...",
17  "templateTags": [{"name": "ref", "type": "card", "cardReference": 10}],
18  "resultMetadata": [
19    {"name": "day", "base_type": "type/DateTime", "semantic_type": "type/CreationTimestamp"},
20    {"name": "order_count", "base_type": "type/Integer"}
21  ],
22  "collectionPath": ["Data", "Orders Team"],
23  "referencedCardIds": [10]
24}
25```
26 
27Use `resultMetadata` to:
28- Map `base_type` to KSL column type: `type/Integer`, `type/Float`, `type/Decimal`, `type/BigInteger` → `number`; `type/Text`, `type/TextLike` → `string`; `type/DateTime`, `type/Date`, `type/DateTimeWithTZ` → `time`; `type/Boolean` → `boolean`.
29- Identify grain candidates: columns with `semantic_type: type/PK`.
30- Identify join candidates: columns with `semantic_type: type/FK` plus `fk_target_field_id`.
31…