Passage Data

Check a file →

The A006 csv: a laboratory's LIMS export, one row per result

Bureau Veritas / NOVA · A006 LIMS export (csv)

What you are seeing — the laboratory's zip holds a csv with columns named EX_LABNUM, EX_SMDESC, EX_RESC, EX_UNITS — every result on its own line — and no software you have reads it as anything but a spreadsheet of codes.

The short answer

A LIMS export is the certificate before it was laid out: one row per (bottle · analysis), the sample description, the laboratory number, the parameter, the result as printed (censored marks included), its unit, the detection limit. It is the most faithful form of the certificate — and the least readable.

What the door says about {lab_a006_file} today, measured: «{lab_a006_headline}», {lab_a006_samples} samples counted, with the sample-id column refused as {lab_a006_code}. That sentence is the door's own, not ours to soften: the long export reads as a monitoring series until its own dialect lands. Until then the N001 xlsx twin in the same package is the table to drop — the package fold already prefers it.

The rest of the answer — 1 more point

The reader for this export is the next build on the laboratory lane (the EX_* vocabulary, the ④ fields kept distinct, the certificate PDF cross-checked against it); this page's numbers are read back from the bench and change the day it lands.

What to drop today

  1. The whole zip the laboratory sent: the N001 xlsx inside it reads as the table, the csv is kept beside it.
  2. Or the N001 xlsx alone. The csv alone reads as a monitoring series today — the headline on this page is what you will see.
Drop the laboratory's zip

The package as the laboratory sent it: the xlsx is read, the exceedance table comes back. Free during the testing period · no account · your rows are discarded after the check.

Check the file you have →

Related