DISCO makes it easy to load in a production received from a different party through the load file ingest feature in the Ingest menu. Your production should be organized in a single folder (Production Volume) before proceeding.
The Production Volume must contain separate sub-folders for the produced document images, natives, and text, as well as at least one index file, often referred to as a load file or metadata load file (.dat). An optional image load file (.opt) can also be included.
The diagram below illustrates the typical components of a Production Volume, including the data and image load files. Your load files can either be loose, at the root of the Production Volume or within a "Data" folder.
To correctly assemble the production's contents using the load file ingest feature, DISCO must be able to map the image, native, and text files to the data load file (.dat) and image load file (.opt). During load file ingest, DISCO compares the file paths in the load file to the file paths of the images, natives, and text within the Production Volume. This includes:
- Confirming that the selected load files are within the Production Volume.
- Validating that paths in the data load file and image load file are relative to the parent directory of the Production Volume.
DISCO has additional prerequisites for load file ingests.
Example Production Volume with load files at the root of the Production Volume.
Example Production Volume with load files in a sub-folder of the Production Volume.
A properly formatted load file uses paths that are relative to the Production Volume folder — meaning each path in the data and image load files begins with a folder inside the selected Production Volume.
NOTE: If a path starts with a drive letter (e.g., C:\…) or points outside the Production Volume, validation will fail.
Example data load file with paths starting from the same parent directory as the Opticon file.
Example Opticon file with paths starting from the same parent directory as the load file.
After field mapping, DISCO checks that the paths in the mapped fields resolve to files available for upload.
- If the unresolvable path is in the first populated row of the column, DISCO surfaces an error during mapping that identifies whether the problem is in the data load file, the image load file, or a mismatched root directory.
- If the first populated path resolves but later rows contain unresolvable paths, the ingest fails validation and the validation report lists the specific lines with unresolvable paths.