How to Structure Your Data Package for Structured Import/Overlay

Overview

When performing a structured import or overlay in VenioOne, the data package must be organized correctly so that VenioOne can locate and validate the files referenced in your load file. Incorrect folder structure is one of the most common causes of path validation failure during import/overlay.

The Key Rule

The paths in your load file must be relative to wherever the load file itself is located. VenioOne resolves file paths starting from the load file's location — so the folder structure and the paths in your load file must match.

Example

A standard production package typically looks like this:

VOL00001\
  ├── loadfile.dat
  ├── TEXT001\
  │     └── 23068_00000001.txt
  ├── NATIVE001\
  │     └── 23068_00000001.docx
  └── IMAGES001\        (if applicable)
        └── 23068_00000001.tif

Here, loadfile.dat sits inside VOL00001, at the same level as the data subfolders. So the paths in the load file should start from the subfolder name:

What if my paths include the top-level folder name?

If your load file paths are written as VOL00001\TEXT001\23068_00000001.txt, that will also work — but only if the load file is placed one level above VOL00001, like this:

Parent Folder\
  ├── loadfile.dat
  └── VOL00001\
        ├── TEXT001\
        │     └── 23068_00000001.txt
        └── NATIVE001\
              └── 23068_00000001.docx

In this case, loadfile.dat and VOL00001 are at the same level, so the path VOL00001\TEXT001\23068_00000001.txt correctly resolves from the load file's location.