Decide where the work belongs
Determine the accepted wrong outcome
Compare a headerless file and a file with real headings. Record whether the wrong choice rejects the import, adds a label record, or drops the first data record. A successful status can be misleading when the lost record has no obvious downstream error or duplicate warning.
Group by actual export layout
Identify which source tools produce headerless files, introductory notes, or multiple heading lines. Estimate the affected import population from available attempts. Avoid grouping every mapping complaint under header detection when the row boundary is correct and only a destination field choice is wrong.
Try correction before and after import
Check whether users can set header presence and confirm the first record before committing. Then estimate the effort to identify an already lost or extra record. A post-import repair that requires a full comparison with the source adds more cost than a clearly labeled preview choice.
What to carry forward
Record priority using silent acceptance, layout reach, preview clarity, and reconciliation effort. Assign a revisit trigger for another producer layout or an accepted missing record. Keep the decision tied to observed row handling rather than the apparent simplicity of adding a header checkbox to the screen.
Technical background: PostgreSQL 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