Jump to content

Production Documents and Your Database

Susanne Strong



By Brittany Thaler, ACP eDiscovery 


We all know that when we produce items in discovery ][ Local, we can automatically have our bates range, or production numbers, populate in a ProdBegNo and  ProdEndNo field. What do we do about documents that are produced to us though?   

Many use the typical workflow of using the BegNo field as a bates range field for these documents and having to search on several fields to encompass all produced documents in the matter. This can be tedious, time consuming, and result in errors. Ingesting the documents using the Bates Number as a BegDoc number is usually where the train stops for most.   

What if we continued down the track and created an overlay for those bates ranges, copying over into existing ProdBegNo, ProdEndNo Fields?  We cannot accomplish this by a global replace, but we can export a simple CSV file containing the BegNo, EndNo, BegAtt, EndAtt, ProdBegNo, ProdEndNo, ProdBegAtt, and ProdEndAtt fields.  Once we have completed the export, we are able to copy over the Beg related fields and paste into the Prod related fields. Easy peasy, right? Enter the Administration portion of discovery ][ local to Import the CSV file as a data overlayNow our bates numbers from opposing counsel are in the same field as items we produced, making searching for production documents simpler and reducing potential for error. 

For more information and in-product education, check out On a Mission: Overlay BegDoc Naming to Production Fields in discovery ][ Local 

Just as the Learning Experience Team has your back with our Blog series, we now have Workflow Wednesday! A short, concise workflow that can increase your efficiency.  Drop us a line at training@iprotech.com with workflows and guidance you would like to see. 



Recommended Comments

There are no comments to display.

  • Create New...