Prepare a Relativity-compatible DAT/OPT load file pair to import document metadata and page-level images into a review workspace
domain: relativity.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Export document metadata as a delimited .dat file, explicitly setting the Concordance-style special-character delimiters Relativity expects rather than plain commas or tabs
Assign each document a unique, consistent identifier (Control Number/Bates number) that will be used to cross-reference the .dat and .opt files
Build the .opt (Opticon) file as a page-level index, with one line per image referencing the Control ID, volume, and image file path
Save the .opt file using ANSI/Western European encoding, as required for Opticon image load files
Include a corresponding .lfp file alongside the .dat/.opt pair if the production also includes native files
Load the files into the workspace via the Relativity Desktop Client or Import/Export functionality, validating field mappings before committing the import
Known gotchas
Relativity's default delimiter set uses non-printable special characters, not commas or tabs — a .dat file generated by a generic CSV exporter will fail to parse correctly unless delimiters are set explicitly to match
The .dat and .opt files must reference matching, consistent Control/Bates identifiers; a mismatch causes documents to load without images, or images to attach to the wrong document
The .opt (Opticon) file specifically requires ANSI/Western European encoding — saving it as UTF-8 or another encoding can silently corrupt the image load
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?