Check whether the outcome improved
Exercise supported schema variations
Import a consistent pair, a reordered file, and a file missing an optional column under the documented rules. Include repeated labels where supported. Compare exact destination assignments and missing-value treatment, keeping expected results independent of whichever schema the importer chooses first when reading the controlled file set.
Check review coverage and mapping
Inspect how each distinct source schema is presented before confirmation. Confirm the selected alignment or per-file mapping reaches execution. Change file order in a separate controlled run to reveal whether results depend on an incidental first-file choice that the user was never asked to review or approve.
Trace final values to source files
Inspect representative saved records from every fixture file and compare their exact fields. Exercise an unsupported ambiguous layout and review its failure message. Confirm it identifies the relevant source rather than silently forcing its columns into a combined schema that cannot preserve the intended meaning of the original values.
What to carry forward
Accept when every supported layout produces the intended assignments regardless of incidental file order and unsupported ambiguity is reported clearly. Record source variants not exercised. Keep verification open if only combined counts or the first file were checked; each distinct schema must be represented in the final value comparison.
Technical background: DuckDB documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow