Input Reference
File Manifest Schema
- File format: CSV (Comma-Separated Values)
- Encoding: UTF-8
- Delimiter: Comma-delimited
- Header row: Required (first row contains column names)
Also see manifest file limits here.
Example of Minimal Manifest
This is an example of a simple manifest, containing required columns (document and subject_id).
Required and Recommended Columns
Additional Optional Columns
For information about file size limits, manifest row limits, and other constraints, see System Limits.
Input Validation
- All manifest fields are validated before processing begins
- If a manifest row fails validation, processing will not start
- Validation checks include:
- Every file in the manifest must be present in the source bucket
- File types are correct for the pipeline (only
.pdffiles are supported) - Files are non-zero bytes
- Additional file-type-specific requirements (e.g. text files must be UTF-8 encoded)
- Any validation error causes the job to be cancelled
- A new job must be submitted after correcting validation errors
Validation Schema
Each row in the manifest CSV is validated against the following JSON Schema:
Key validation rules:
- All string fields have a maximum length of 255 characters
documentandsubject_idare required fields- Date fields (
chartdate,subject_dob) must use ISO 8601 date-time format - All other fields are optional
Troubleshooting Input Validation Errors
Manifest validation occurs on job submission; failures may result in one of the following errors:

