Documents produced from other eDiscovery platforms are delivered in a format which includes “load files”. These files instruct the database where each document begins and ends.
When documents are produced in this format a series of folders delivered and often labeled DATA, IMAGES, NATIVE, OCR depending on the contents of the production. The documents MUST be kept in this folder structure and all available on the server for the load files to accurately import the data.
The OPT or DAT load file will be located in the DATA folder: (see far below for full details of how the tool reads and processes the OPT file). If the files are in a container such as a zip file they must be first removed from the container (unzipped).
To add documents to a matter, create a Collection:
Switch to the Process menu:
Right-click on the "Collections" node or an existing collection and select New Collection.
A new collection node appears in the collection tree and is editable.
Drag and drop the DAT file onto an existing collection node in the collections tree OR drag and drop onto the imports grid (if only OPT file provided drop it to the collection). The Add Production interface will appear.
When the production also includes a DAT file, the Image Path, Native Path and Text Path will be updated with the information from the DAT. While the tool detects the Bates Field, Image Path, Native Path and Text Path from the DAT file, these fields are editable if modifications are needed.
When no DAT is provided, the tool will predict the location of the files. These fields are editable if the prediction does not meet expectations.
At the beginning of processing, the tool will audit the production and report any deficiencies. These reports are exportable with the intention of containing the information the producing party would need to correct the error. Click on the highlighted "copy" button to copy the text to the computer's clipboard. Select YES to load the documents where are complete for review while awaiting a corrected production from the producing party.
To overlay the fielded data from the DAT, please see the section on Overlaying Metadata