Import & mapping

provenance survives the import synthetic demo data
31
rows awaiting mapping review
7
canonical record types mapped to
100%
rows retaining original source + timestamps

Batches

members keep their own systems — Proof maps, never absorbs
BatchFromMappingState
SOM_lab_0341.csvMidland Agronomy · LIMS 28 → Outcome · 3 unmapped (unit unclear)review below
operations_2026_q2.jsonFen Growers · co-op platform 112 → Recorded action · terminal timestamps nativemapped
trials_archive_2024Northern Trials Network protocol + comparison chains reconstructed · deviations flagged honestlymapped

Mapping review · SOM_lab_0341.csv

1 row needs a decision
Incoming rowMaps toOriginal source
row 12 · field FG-112 · 4.2 "%LOI" Outcome PRF-UK-N-004112 family MAG LIMS · 14 Jun 10:22mapped
row 13 · field FG-114 · 3.8 "%LOI" Outcome MAG LIMS · 14 Jun 10:22mapped
row 14 · field FG-117 · 41 "g/kg?" unmapped — unit ambiguous MAG LIMS · 14 Jun 10:22

Ambiguity becomes a query to the contributor, never a silent guess. The original file, its hash and native timestamps stay attached to every mapped record.

Import rules: incoming data maps to the seven canonical record types; original source and timestamps survive on every row; unmapped rows wait for a decision — imported evidence never loses its origin.