Admin / Ingest
Upload data
SJ
Ingest - Data intake & mapping studio - Step 1 of 7
Upload your CSV file
Source files are profiled, mapped, validated and audited before they can land in raw_upload or raw_airbyte. No data lands until a steward has approved the mapping profile.
1
Upload CSV2
Discover fields3
Suggest mappings4
Validate preview5
Approve profile6
Load raw landing7
Request refreshTarget entity
Choose the canonical entity this file maps to. The entity determines which columns are expected and which validation rules apply.
6 entities available. Each has a fixed schema in the warehouse.
Shown in audit trail and governance centre.
CSV file
Drop your file below. Headers must be in row 1. The live intake backend accepts CSV text in this phase.
Drag a CSV here or click to browse
.CSV files only - max 10 MB - headers required in row 1
The uploaded CSV is profiled in-browser, then sent to the backend discovery and validation endpoints. Any successful load writes audit evidence and a refresh request.
Mapping profile
The current live route uses the discovered field set and the existing backend mapping APIs. Full manual profile editing remains available in Mapping Studio.
Auto-suggest
Profile columns and propose canonical mappings.
Use approved profile
0 approved profile(s) available in studio.
Map manually
Manual field editing continues in Mapping Studio.
Auto-suggest profiles your columns and proposes canonical mappings. A steward approval is still required before any rows land.
Discover fields unlocks after a file is selected.
No data lands in the warehouse until step 6. All mapping decisions are recorded in the audit trail.