All Collections
Upload
Upload Checklist
Upload Checklist

How to ensure quality control in your eDiscovery uploads

Jury Joves avatar
Written by Jury Joves
Updated over a week ago

Did everything transfer correctly?

With File Uploads, you may want to confirm that all items from the source location successfully transferred and processed. To do this, you can compare the document counts between pre-processed and post-processed items. To find the pre-processed count use File Properties in Windows or Get info on a Mac to count the number of files in a folder. To find the post-processed count, in Logikcull, use the Upload filter to select a particular upload, switch to No Dedupe view, and use the Family filter for parent and standalone items only. The result should come close to the original file count before ingestion.

In addition, check the expected File or Email metadata information from the load file such as document date, file path, email from/to/cc/bcc, etc. are viewable in Logikcull.

NOTE: Container or archive files such as Zips, RAR, PST, MBOX or LEF (L01) are not retained in Logikcull once expanded.

Are Custodian names properly associated to the uploaded data set?

You can use the filter carousel to ensure the correct custodian is associated with their corresponding data.

Use Auto Tags (QC Tags) to check images, natives, and text files.

Where applicable, check that the images, natives, and text are available in the document viewer. Use Auto Tags such as “Not Rendered”, “Has No Native”, “Has No Text”, “Zero Bytes”, “OCR Failed”, and “Failed Extraction” to quickly identify them. Please note that some images may reflect slip sheets as intended if the file format is unsupported, invalid, corrupt or not available from the 3rd party production.

Check family status.

If parent-child exist, also known as a document family, utilize the Family Status carousel filter to verify that “Is Parent” and “Is Child” items are properly identified.

Check deduplication views.

Compare deduplication views to check that family-level duplicates are automatically sequestered.

Did this answer your question?