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 LFP 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 lfp or opt file onto an existing collection node in the collections tree OR drag and drop onto the imports grid. The Add Documents interface will appear.
Imports of data from load files may necessitate the option to de-select “expand containers” if the data provided by the producing party has containers not intended to be produced as separate documents. For example, when Excel files have embedded documents which upon expanding become an unintended produced document without a Bates number.
If your DATA folder also contains a load filed labeled as a DAT extension, please see the section on overlaying metadata:
When DWR processes data with an OPT it reads the opt and loads the images from the Images Path from the OPT. It then crawls the folder structure and looks for any Native files and text files that have the exact same name as the BegBates in the OPT.
As an example when an OPT starts line reads
the tool will stitch together ABC-00001234 and ABC-00001235 (which must be in the path VOL001,IMAGES\00\000\) into a multipage image and copy to the repository. DWR will also look in the VOL001 folder structure for any Native file labeled ABC-00001234 and any Text file labeled ABC-00001234.txt and also match those to the same record.
If your text isn't loading (or the natives) be sure the producing party named them with the correct naming structure.
For the Metadata overlay we recommend using the Load File Key to be the XFER as the tool also populates the XFER with the exact naming convention of the files on disk. We found way too often the DAT files match the name on disk and that does not always match the BATES numbers.
DWR "normalizes" all BATES information for the BATES column and it will always be eight pad. The XFER field will match the images on disk naming.