Production Uploads in Logikcull allow you to bring externally processed data into the application for search and review. This could be data provided by another party, such as a legal document production or data processed by a vendor. You can use load files, which contain metadata and file location information, to import these already processed documents into Logikcull.
ℹ️ after you've uploaded your Production Upload, you can review documents in Bates order by sorting the upload by "Imported Beg Bates."
Starting a Production Upload
Go to the Uploads tab, click the "+" New button, and select "Production Upload" from the drop-down list.
Select file types to upload
On the first page, choose "I'd like to import a data load" and checkmark Images, Natives, and/or Text based on what was provided by the producing party. Look for subfolders titled "Images," "Natives," and/or "Text" in your production volume to identify the content.
Upload load files
Locate the load files (usually in a folder named DATA) and upload them. The top box is for .DAT or .CSV files, while the bottom box is for .OPT or .LFP files.
⚠️ Depending on how your production was received, the load files may already be in a compressed zip folder. If that's the case, you'll need to extract the contents of the zip first, then drag and drop the load files into Logikcull.
If the images are in multi-page PDF/TIFF format and the filenames are named by the bates number, attaching an image load file (i.e. OPT/LFP file) is optional.
Map your import fields
Logikcull suggests matches based on field name similarity, marked in green. Verify the mappings are correct, referring to field definitions and sample data from the load file.
All fields must be mapped before proceeding. You can import them into an existing Logikcull Document field, import as a new custom field, or choose not to import them.
💡 Helpful Tips for mapping
If there is no corresponding Logikcull field, importing as a new field allows the metadata to remain searchable.
You can reuse mapping templates for productions from the same party. Load a saved template or create one for future use.
For a large number of fields, use the "bulk map" dropdown to quickly select unmapped/mapped fields or reset selections.
Zip and upload the volume
Use a recommended zip utility to compress the (DATA, IMAGES, NATIVES, TEXT folders), making sure the folder structure is exactly as outlined in the load file. Upload the compressed file with a .zip extension. Provide a name for the import. You can choose to attempt OCR on documents without text or render an available native if there is no image, enabling image rendering and searchability.
If the archive is password protected, you must remove the password prior to uploading into Logikcull, then re-zip so that you upload the unprotected version of the volume.
For productions that include data sets with multi-page images in PDF or TIFF that are each named by their corresponding bates (begin doc) number, e.g. BATES000001.pdf or BATES0000001.jpg, you can skip loading an image reference load file OPT or LFP. Logikcull will automatically locate the images and load accordingly (i.e. common with Relativity productions).
NOTE: If you would like to use the text given by the producing party to search by, you will want to make sure that you mapped a "text file link" during step 2. With this option, the searchable text may be more reliable, but searching on the actual image itself for keywords depends on if the document have a text layer prior to upload. If not, you will have to use the "text" view of the document to scroll through any text hits. If you would like to search for keywords on the actual image, you would want to not import a "text file link", and make sure you choose the option to "attempt OCR if no text detected". However, please note that this may cause the upload to take longer to complete, and the size of your upload may expand more than expected due to the processing needed to be done. Moreover, text files can technically be loaded without a "text file link" in the metadata file, as long as the text files themselves are named with their corresponding bates (begin doc) number, e.g. BATES000001.txt. In addition, Logikcull will automatically locate and load searchable text in these cases.
If you run into any errors or have any questions about this workflow, feel free to contact our support team through in-app chat!