Structure Load Files for Ingest
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.
In order to correctly assemble the productions 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 DISCO load file ingest, the file path values in the load file are automatically compared to the file path of the images, natives and text within the Production Volume. This includes
- Confirming that the selected load files are within the Production Volume and
- Validating that paths in the data load file and an 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 should have paths to the Native files and Text files, relative to the Production Volume folder.
NOTE: Paths being relative means the filepaths in the data and image load files must begin with a path in the selected Production Volume folder. If a path in the load file starts with a letter drive or somewhere different from the selected production folder, the checks 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 mapping fields during a load file ingest, DISCO will perform checks to resolve the paths of mapped fields to verify the referenced files are available to upload.
If the unresolvable path is in the first populated line of the column, then DISCO will present an error during mapping that will identify whether the problem is within the data load file, image load file, or with different root directories.
If the first populated path resolves but there are unresolvable paths on other rows in the ingest, the ingest will fail validation and the validation report will identify the specific lines with unresolvable paths.
