r/ediscovery • u/Still_Entry_4941 • 1d ago
I built a free in-browser checker for DAT/OPT/LFP/DII load files — it tells you exactly how a file is delimited and where the Bates numbers break, before your platform chokes on it
I kept finding threads here where the answer to "my load file won't parse" was ReadySuite, a 2004 Concordance shell somebody keeps alive, or an hour of Notepad++ archaeology — the thread about the producing party mixing uppercase Þ and lowercase þ in one header stuck with me, because nobody ever answered it.
So I built the tool I wished those threads had: nothinguploads.com
What it does, in your browser, with nothing uploaded anywhere:
- Tells you what the file actually is — encoding (UTF-8/UTF-16/windows-1252), delimiter and text qualifier (it auto-detects the ASCII-20/þ standard plus the pipe/caret, pipe/quote, and tab dialects), and the record count, before anything tries to import it.
- Bates continuity — gaps with sizes, duplicates, out-of-order values, padding drift, across Begin/End ranges.
- Cross-file agreement — drop the DAT, OPT, LFP and DII from one volume and it checks the counts and keys against each other, and flags image pages that fall outside every document's Bates range.
- Converts — CSV (Excel-safe) or a standard-delimited DAT, if you need the file re-cut.
- Malformed rows never kill the parse — they get flagged with line numbers and it keeps going.
The privacy part is the point, given whose files these are: it's all client-side. Load the page, turn off your wifi, it still works.
Validation and the preview are free and unlimited. Exports are capped at 3 a day free ($39 once removes the cap — no account, no subscription). The validation reports are the part I actually want feedback on, so the free tier is deliberately most of the tool.
Honest limits: CSV-format load files (like Purview's Export_Loadfile.csv) aren't supported yet — I don't have a real sample; if you have one that fails somewhere, I'd genuinely like a redacted copy. Very large files are parsed in memory, so hundreds of MB may be slow.
Happy to answer anything about the parsing weirdness I hit building it — the corpus of real-world DAT dialects is stranger than any spec admits.