Load files map produced documents to their metadata and establish page and document boundaries. Common formats include DAT files for metadata fields and OPT or LFP files for image references.

Field lists and delimiters must match what the receiving platform expects.

Alternative Names:

Load Files, DAT File

Why it Matters?

Load file defects are the most common technical production dispute, and they are entirely preventable. A field delimiter mismatch, an unexpected field order, or missing document boundary markers can make an otherwise complete production unusable until corrected. Specifying the exact field list and delimiters in the protocol and verifying with a small test load before the full production eliminates nearly all of these disputes.

Frequently Confused with

Frequently asked questions

What does a load file contain?

What does a load file contain?

Metadata field values, document and page boundaries, and paths to image, native, and text files for each produced document.

How are load file disputes avoided?

How are load file disputes avoided?

By specifying exact fields and delimiters in the protocol and verifying a small test load before the full production is delivered.