Production Uploads

How to set up, map, and import your Production Upload

John OHara avatar
Written by John OHara
Updated over a week ago

Walk-Through Video

What is a Production Upload?

Production Uploads allow you to bring data that's been processed outside of Logikcull into the application for search and review. Often, this will be data produced to you by another party, such as a legal document production or data processed by a vendor. With Database Imports, you can pull these already processed documents into Logikcull using special files, called load files, which contain metadata and file location information about the documents in the collection.

How to Check Your Upload for Production Upload data

If data was sent to you for upload, check the contents for important clues - it might be a Production Upload!

Another indicator you might see if you attempt to upload production upload data as a file upload is a warning message. This is likely a good indication you should re-start you upload as a production upload.

How to Upload a Production

Step 1: Getting Started

Go to the Uploads tab, click the "+" New button, and select "Production Upload" from the drop-down list.

Select "I'd like to import a data load" and checkmark Images, Natives and/or Text, depending on what was provided by the producing party. Usually, the production should have subfolders titled "Images", "Natives" and/or "Text" that will let you know what was provided.

Step 2: Upload load files

Prior to zipping up the volume, find the load files (usually contained in a folder named DATA). Drag and drop, or click to upload your load files. The top box is for .DAT or .CSV files; the bottom box is for .OPT or .LFP files.

  • Helpful Tip: 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.

Step 3: Mapping and validation

Map your import fields. Logikcull will automatically map suggested matches based on the similarity of the field names, and mark the rows in green. It is recommended to check that they are mapped correctly; the definition of the field and the sample data that pulls from the first three lines of your load file can help as references to confirm or modify this choice. All fields will have to be mapped before you can move on to the next step. When mapping any fields, you can either choose to: (1) import them into an existing Logikcull Document field, (2) import them as a new custom field, or (3) not import them.

💡 Mapping Tips

  • If there is no corresponding Logikcull field for one of the imported fields, it may be helpful to choose the "import as a new field" option so the metadata is still searchable in Logikcull, as needed.

  • Mapping templates can be re-used when uploading productions from the same producing party, as the fields are expected to be consistent. If you already have one saved from a prior database upload that you'd like to use, you can load this from the dropdown at the top right. If not, it is recommended that you save a mapping template via the option at the bottom left.

  • If you have a large number of fields, you can checkmark select fields, or use the "bulk map" dropdown to quickly select unmapped/mapped fields, or deselect all fields. Then, you can choose to "import as new", "do not import", or "reset to Logikcull selections" in a single action.

💡 Field Mapping Guide

The table below provides guidance for mapping some of the less intuitive field names so that metadata and file locations can be correctly communicated to Logikcull.

Logikcull Field Mapping

Common Field Names

Begin Bates


End Bates


Begin Family

BegAttach, BEGATT, BeginAttachmentBates, ATTACH_START

End Family

EndAttach, ENDATT, EndAttachmentBates, ATTACH_END

Page Count


File Path

(the original document file path)


Native File Link

(the relative file path to the uploaded volume)


Text File Link


Click here 🔗for more detailed information on the mapping step

Production upload fields

During Step 3 of the Database Upload, Logikcull will map existing fields in your load file to corresponding fields within Logikcull.

However, you may be asked to map additional fields in your load to existing fields that Logikcull was unable to reconcile. The table below provides further clarification as to what information each field contains.

Control Numbers

Begin Doc

The beginning control number of a document, i.e., the number of the first page.

End Doc

The ending control number of a document, i.e., the number of the last page.

Family ID

The control number that identifies members of a document family. This is the Begin Doc number of the family's parent document.

Begin Family

The beginning control number of a document family, i.e., the number of the first page of the first document in the family.

End Family

The ending control number of a document family, i.e., the number of the last page of the last document in the family.

Begin Attach

The beginning control number of a document's attachments, i.e., the number of the first page of the first attachment in the family.

End Attach

The ending control number of a document's attachments, i.e., the number of the last page of the last attachment in the family.

Special Fields


The person having administrative control of a document or electronic file; for example, the data custodian of an email is the owner of the mailbox which contains the message.

Native File Link

A link to a copy of the original file.

Text File Link

A link to the extracted text file.

Email Metadata

Email From

The original author of the email.

Email To

The intended recipients of the email.

Email CC

The carbon copied recipients of the email.

Email BCC

The blind carbon copied recipients of the email.

Email Subject

The email subject line.

Email Date Sent

The date the email was sent.

Email Time Sent

The time the email was sent.

Email Date Received

The date the email was received.

Email Time Received

The time the email was received.

File Metadata

File Name

The document's original name in the file system.

File Path

The document's original location in the file system; a breadcrumb.

Full Text

The full extracted text or OCR of the document.

Document Date

The date of the individual document.

File Size

The original file size, in bytes, of the document.

File Author

A file metadata tag that shows the name of the author for the document.

File Last Saved By

A file metadata tag that shows the name of the person who last saved the document.

File Company

A file metadata tag that shows the company name.

File Keywords

A file metadata tag that shows various keywords applied to a document. Not from search.

File Title

A file metadata tag that shows the title of the document.

File Comments

A file metadata tag that shows comments in the document.

File Subject

A file metadata tag that shows the subject of the document.

File Revision Number

A file metadata tag that shows the number of revisions in the document.

File Date Created

A file metadata tag that shows the date the document was created.

File Time Created

A file metadata tag that shows the time the document was created.

File Date Last Modified

A file metadata tag that shows the date the document was last modified.

File Time Last Modified

A file metadata tag that shows the time the document was last modified.

Step 4: Upload your data

Zip up the production volume (DATA, IMAGES, NATIVES, TEXT folders), making sure the folder structure is exactly as outlined in the load file. Upload the data volume. This should be the entire set of images/natives/text files provided as a compressed file with .zip extension. Input a name for this import. You can checkmark the option to attempt OCR on documents if no text is detected, or render an available native if no image is detected, so that Logikcull can render images and make your documents searchable.

  • 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.tiff, 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.

What is an Overlay?

An overlay is a process of updating and/or replacing metadata, images, natives, or text on existing database uploads.

When should Overlays be applied?

  • You received a production with poor quality images or text, you can now request an overlay and add them to Logikcull without losing work product. Logikcull will re-index the overlaid text automatically.

  • You received natives and placeholder images as a production. Now you can re-image the natives in Logikcull and create your own overlay to replace the placeholders.

  • You received a production but realize some of the metadata is missing. You can now request a supplemental delivery of just the metadata and add it to Logikcull.

What can't be overlaid?

  • Family Relationships

  • Tags can be imported as metadata but will not populate as tags.

  • Notes can be imported as metadata but will not populate as notes.

  • Comments can be imported as metadata but will not populate as comments.

  • Custodians cannot be overlaid to Logikcull's custodian field, but can be imported as new as a searchable field.

Step by Step Instructions

⚠️ An overlay is only possible if the data was uploaded as a database upload.

  1. The option to do an overlay is available under the uploads tap, when you click (+)"Create a new..." (item 1). Select "Production Upload" from the drop down menu.

2. Choose “I’d like to import an overlay” (item 2) and select what's being overlaid with new data [Load File, Natives, Images Text] (item 3)

⚠️ NOTE: Like database upload, load files are a must! If you're overlaying the Native File Link or Text link, you will need to check "Natives" and/or "Text" accordingly.

Tip: Select checkboxes anything you plan on replacing (Example: If you are trying to overlay an image, the Image option should be selected)

3. Drag-and-drop the updated overlay load file (item 4). If images are being overlaid, drag-and-drop the updated OPT file (item 5). An OPT may not be required if images are multipage and named as the cross-reference index in the load file (usually Beg Bates).

4. Select the “Overlay Cross-Reference Number” (item 6) (item 7) and then map only the field(s) that are being overlaid with new data (item 8). Any metadata that isn't being overlaid can be ignored (Do not import).

What is an Overlay Cross-reference number? It is a field that Logikcull uses as a reference to locate the document(s) for which the overlay needs to be applied.

⚠️ Beg Bates as used in Database Uploads or Logikcull ID are currently the only two fields accepted as overlay cross-reference number).

5. Once the fields have been mapped, you can name your overlay. Then, drag-and-drop the zip folder with any files associated with the overlay (Tip: Already have OCR text files? It is advisable to NOT select the OCR option)


Resolving "Missing image/native/text" Data Volume Warnings in Database Uploads

The vast majority of these errors are caused by misalignment between the relative file path reported in a load file and the actual location of those documents in the volume.

When zipping up your volume, make sure that the folder structure in the volume matches the file path in the load file for your natives and text files exactly.

Please note that the Error log provides the first instance of the error. The number to the right of the sample error, in the "occurrences" column, indicates how many times that particular class of error occur in the upload.

Use the error report to verify the expected file path. The Error Report might show errors like this:

(warning) Line 2: Missing text file for PROD00000001: VOL001\TEXT\PROD00000001.txt
(warning) Line 1: Missing image file for PROD00000001: PROD00000001.pdf
(warning) Line 3: Missing text file for PROD00000002: VOL001\TEXT\PROD00000002.txt(
warning) Line 2: Missing image file for PROD00000002: PROD00000002.pdf

Using the error report can be handy here since it will point to specific lines where the files are missing.

For example, this sample excerpt indicates that VOL001\TEXT\PROD00000003.txt and its corresponding corresponding PROD00000003.pdf is missing.

(warning) Line 4: Missing text file for PROD00000003: VOL001\TEXT\PROD00000003.txt
(warning) Line 3: Missing image file for PROD00000003: PROD00000003.pdf

Using the indicated file path, navigate to your extracted zip and ensure that these files are located within.

If the indicated file is missing from its folder, Logikcull will throw the above errors.

This fix would necessitate going back to the producing party and requesting the missing documents, and an updated load file.

Checking the Native/Text file path in CSV/DAT load file:

Assuming the files are located in their correct folder, and are accounted for, the next step would be to ensure that your zip file structure matches up with the expected file structure in the load file.

For example, if the database volume directory leading to a Native File is structured like this:

The Native File Link in your load file needs to mirror that structure, with the same folders and subfolders leading to the file, like this:

⚠️ Be careful to make sure the top-level zip folder is not included in the directory.

Checking the image file path in OPT/LFP:

The same rule goes for your Image files, respectively; although your Image file links will be located in an image load file (OPT or LFP).

You should ensure that your zip file has this same expected structure when uploading to Logikcull.

For example, the first folder you would want to see in your zip would be a folder called “VOL001” if you had a structure similar to that one.

Ensuring that your zip file has an identical structure to the one specified in your load file will clear the errors in the upload.

Downloading validation error reports

At certain stages of your database upload, you may encounter validation errors. To help with troubleshooting, you may download those errors to your computer. Just click "Download error report" on the screen where the error is presented to you:

💡 Click here 🔗 for a detailed load file troubleshooting guide.

Did this answer your question?