PREPROD
ReaderAuthor

piper

Import Batch

An ImportBatch represents one lab report file uploaded to Piper. It tracks the file's origin (fileName, fileType, fileSize, labName, labReportId), how it was parsed (extractionMethod, extractionConfidence, profileId, columnMapping), row-level statistics (totalRows, validRows, warningRows, errorRows), and lifecycle timestamps (uploadedAt, parsedAt, committedAt).

1 min read · 2 depth levelsstratum-piper · vdevMatches production
Everyday

Every time a groundwater lab delivers a data file, Piper creates an ImportBatch to manage that file through the entire ingestion process. After upload, the batch is parsed using the matching ImportMappingProfile detected by headerFingerprint or manually chosen. The status field progresses from upload through parsing to commit. During validation, any rows with problems become ImportValidationIssues attached to the batch. Once committed, the batch's rows become permanent AnalyticalResults linked to the site. The row counts (totalRows, validRows, warningRows, errorRows) give compliance staff an at-a-glance quality summary before they approve a commit.

Technical section
Data model, API, and internals — visible to developers.
View as developer →
Was this helpful?