Close
Enter your
text here

Processing

Court Allows Costs for TIFF Conversion and OCR, Likens it to “Making Copies” – eDiscovery Case Law

In Kuznyetsov v. West Penn Allegheny Health Sys., No. 10-948 (W.D. Pa.Oct. 23, 2014), Pennsylvania Senior District Judge Donetta W. Ambrose upheld the Clerk of Courts issuance of Taxation of Costs for $60,890.97 in favor of the defendants and against the named the plaintiffs, including costs for “scanning and conversion of native files to the agreed-upon format for production of ESI”.

Case Background

The plaintiffs filed a collective action pursuant to §216(b) of the Fair Labor Standards Act (“FLSA”) against the defendants, which was ultimately decertified as Judge Ambrose ruled that the 824 opt-in plaintiffs were not similarly situated.  After that, the plaintiffs filed a Motion for Voluntary Dismissal, which Judge Ambrose granted, dismissing the claims of the opt-in Plaintiffs without prejudice and dismissing the claims of the named Plaintiffs with prejudice (the plaintiffs appealed and the Third Circuit dismissed the appeal for lack of jurisdiction).

On October 15, 2013, the defendants filed a Bill of Costs seeking a total of $78,561.77. On October 31, 2013, the Clerk of Courts filed a Letter calling for objections to the Bill of Costs, which was followed in January of this year by objections from the named plaintiffs (to which the Defendants filed a response). On August 1, the Clerk of Courts issued his Taxation of Costs in the amount of $60,890.97 in favor of Defendants and against the named Plaintiffs.

Judge’s Ruling

Stating that “Rule 54(d)(1) creates a strong presumption that costs are to be awarded to the prevailing party”, Judge Ambrose analyzed the costs as defined in 28 U.S.C. § 1920, including §1920(4), which covers “Fees for exemplification and the costs of making copies of any material where the copies are necessarily obtained for use in the case”.

Addressing the plaintiff’s contention that the costs awarded were for eDiscovery costs were not necessary and were awarded at unreasonably high rates and referencing the Race Tires case in her ruling, Judge Ambrose stated:

“With regard to unnecessary e-discovery costs and unreasonably high rates, Plaintiffs first argue that the costs associated with Optical Character Recognition (‘OCR’) were unnecessary…As Defendants point out, however, Plaintiffs requested the information be produced in, inter alia, OCR format…The ‘scanning and conversion of native files to the agreed-upon format for production of ESI constitutes `making copies of materials’ as pursuant to §1920(4)…Accordingly, I find the costs associated with OCR conversion are taxable.

Furthermore, I do not find the cost of 5 cents per page for TIFF services to be unreasonably high, nor do I find 24 cents per page for scanning paper documents to be unreasonably high…Consequently, I find not merit to this argument either.”

Rejecting the plaintiff’s arguments that “1) Defendants have unclean hands; 2) Plaintiffs are unable to pay the costs; and 3) it would be inequitable to force the three named Plaintiffs to pay the entire costs of defending against the claims of the opt-in Plaintiffs”, Judge Ambrose affirmed the amount of $60,890.97 in favor of Defendants.

So, what do you think?  Should the costs have been allowed for conversion of native files when they may have already been usable as is?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Want an Automated, Easy and Inexpensive Way to Process Your Data? Read On – eDiscovery Trends

A couple of months ago, we had a laugh at Ralph Losey’s post that took a humorous look at the scenario where it’s Friday at 5 and you need data processed to be reviewed over the weekend.  It was a funny take on a real problem that most of us have experienced from time to time.  But, there may be a solution to this problem that’s automated, easy and inexpensive.

Anytime we talk about something that relates to our company, CloudNine Discovery, we always add the “shameless plug warning” to let people know that the topic relates to our software or a service we offer.  If you’re a regular reader of our blog, you know it doesn’t happen that often.  But, we have just made a major announcement that we believe will interest many of you.

Today, we are officially announcing the release of OnDemand Discovery®, our new application that enables you to upload your native data and have it processed and loaded directly into OnDemand®, our cloud-based online review tool.

It’s a 100% automated upload process that includes native file extraction from container files (such as Outlook PSTs and ZIP Files), metadata & text extraction and indexing, OCR of image files, duplicate identification and HTML creation, streamlining the process to get started reviewing documents for discovery.  The process automatically notifies you when we’ve received your data and then again when we’ve loaded and indexed it and when all processing (including advanced analytics for early data assessment) is complete.  So, you never have to wonder about the status of your processing job.

It’s ideal for situations where you receive data late on a Friday afternoon and have to get it ready to review over the weekend and also ideal for preparing small batches of files for review without having to run them through cumbersome processing software built for multiple gigabytes, not a small batch of files.  OnDemand Discovery is designed to handle two megabytes, two gigabytes or two hundred gigabytes or more!

There are three easy steps to give it a try:

  1. Sign up for a free account here.  You will receive an email with your credentials (including temporary password), to get started.
  2. When you first log in, you’ll see a button to “Upload Data”.  That will take you to a form to download the OnDemand Discovery client (which is a Windows based client application that resides on your desktop) for uploading data for processing.  Download and install the client to upload data.
  3. Once the client is downloaded and installed, launch the client, log in with your newly created credentials and simply follow the wizard prompts to upload the desired data set and put it into the project of your choice (which you can create if it doesn’t already exist).  It’s that easy!

For more information, feel free to check out our press release on our news page here.  You can also contact me at daustin@cloudnincloudnine.comm for more information as well.

And, as always, please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Be Afraid, Be Very Afraid – eDiscovery Horrors!

Today is Halloween.  Every year at this time, because (after all) we’re an eDiscovery blog, we try to “scare” you with tales of eDiscovery horrors.  This is our fifth year of doing so, let’s see how we do this year.  Be afraid, be very afraid!

Did you know that overlaying Bates numbers on image-only Adobe PDF files causes the text of the image not to be captured by eDiscovery processing applications?

What about this?

Finding that the information was relevant and that the defendants “acted with a culpable state of mind” when they failed to preserve the data in its original form, New York Magistrate Judge Ronald L. Ellis granted the plaintiff’s motion for spoliation sanctions against the defendant, ordering the defendant to bear the cost of obtaining all the relevant data in question from a third party as well as paying for plaintiff attorney fees in filing the motion.

Or this?

It’s Friday at 5:00 and I need 15 gigabytes of data processed to review this weekend.

How about this?

Ultimately, it became clear that the defendant had not exported or preserved the data from salesforce.com and had re-used the plaintiffs’ accounts, spoliating the only information that could have addressed the defendant’s claim that the terminations were performance related (the defendant claimed did not conduct performance reviews of its sales representatives).  As a result, Judge Kemp stated that the “only realistic solution to this problem is to preclude Tellermate from using any evidence which would tend to show that the Browns were terminated for performance-related reasons”…

Or maybe this?

Could an “unconscionable” eDiscovery vendor actually charge nearly $190,000 to process 505 GB and host it for three months?  Could another vendor charge over $800,000 to re-process and host data (that it had previously hosted) for approximately two months?  Yes, in both cases (though, at least in the second case, the court disallowed over $700,000 of the billed costs).

Scary, huh?  If the possibility of additional processing charges for your PDF files, sanctions because you didn’t preserve data in its original format or preserve it in your cloud-based system or inflated eDiscovery vendor charges scares you, then the folks at eDiscovery Daily will do our best to provide useful information and best practices to enable you to relax and sleep soundly, even on Halloween!

Then again, if it really is Friday at 5:00 and you need 15 gigabytes of data processed to review this weekend (inexpensively, no less), maybe you should check this out.

Of course, if you seriously want to get into the spirit of Halloween, click here.  This will really terrify you!  (Rest in Peace, Robin)

What do you think?  Is there a particular eDiscovery issue that scares you?  Please share your comments and let us know if you’d like more information on a particular topic.

Happy Halloween!

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Those Pesky Email Signatures and Disclaimers – eDiscovery Best Practices
 

Are email signatures and disclaimers causing more trouble than they’re worth?  According to one author, perhaps they are.

Earlier this week, Jeff Bennion wrote an interesting post on the Above the Law blog (‘Please Consider the Environment Before Printing’ Email Signatures Are Hurting the Environment) where he noted that, about 5 years ago, people started putting ‘Please consider the environment before printing this e-mail’ in their email signature (along with a webdings font character of a tree).

Bennion states that this is “the Kony 2012 of the environmental battles – it’s a noble war, but a pointless battle” and that the printing of emails is only a tiny fraction of the paper that lawyers waste.  Instead, he notes, “the ‘please consider the environment’ email signature is more like one of those ‘I voted’ stickers — both serve no purpose other than proclaiming your self-righteousness for performing a civic duty”.

In fact, per a Time magazine article, the internet accounts for a good deal of the pollution in the world. In a 2011 article, cleantechnica.com reported that there were about 500,000 data centers in the world and each used 10 megawatts of energy a month.  That’s a lot more than 1.21 gigawatts.  Great Scott!

When comparing Word files containing data that might go into an email with the same data that also includes the email signature, Bennion observes that the one with the email signature contains .3 KB more of data than the one without the signature.  He extrapolates that out to 27,000 GB of extra useless data being added to internet storage servers every day (10 million GB per year) over all business emails, while acknowledging that not all 90 billion business emails are including the signature.  “The point is that it is a pointless gesture that, as a whole, does more harm than good”, Bennion states.

And, the same holds true for those confidential and privileged email disclaimers at the bottom of emails, which he observes “take up about 10-20 times more wasted space than the ‘please stop printing your emails’ disclaimer” – “roughly the environmental equivalent of clubbing 3 baby seals a month”.  Some interesting takes.

These email signatures and disclaimers also affect eDiscovery costs, both in terms of extra data to process and also host.  They can also lead to false hits when searching text and affect conceptual clustering or predictive coding of documents (which are based on text content of the documents) unless steps are taken to remove those from indices and ignore the text when performing those processes.  All of which can lead to extra work and extra cost.

So, what do you think?  Do you use “please stop printing your emails” signatures and confidential and privileged email disclaimers?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Text Overlays on Image-Only PDF Files Can Be Problematic – eDiscovery Best Practices

Recently, we at CloudNine Discovery received a set of Adobe PDF files from a client that raised an issue regarding the handling of those files for searching and reviewing purposes.   The issue serves as a cautionary tale for those working with image-only PDFs in their document collection.  Here’s a recap of the issue.

The client was using OnDemand Discovery®, which is our new Client Side add-on to OnDemand® that allows clients to upload their own native data for automated processing and loading into new or existing projects.  The collection was purported to consist mostly of image-only PDF files.  PDF files are created in two ways:

  1. By saving or printing from applications to a PDF file: Many applications, such as Microsoft Office applications like Word, Excel and PowerPoint, provide the ability to save the document or spreadsheet that you’ve created to a PDF file, which is common when you want to “publish” the document.  If the application you’re using doesn’t provide that option, you can print the document to PDF using any of several PDF printer drivers available (some of which are free).  These PDFs that are created usually include the text of the file from which the PDF was created.
  2. By scanning or otherwise creating an image to a PDF file: Typically, this occurs either by scanning hard copy documents to PDF or through some sort of receipt in an image-only PDF form (such as through fax software).  These PDFs that are created are images and do not include the text of the document from which they came.

Like many processing tools, such as LAW PreDiscovery®, OnDemand Discovery is programmed to handle PDF files by extracting the text if present or, if not, performing OCR on the files to capture text from the image.  Text from the file is always preferable to OCR text because it’s a lot more accurate, so this is why OCR is typically only performed on the PDF files lacking text.

After the client loaded their data, we did a spot Quality Control check (like we always do) and discovered that the text for several of the documents only consisted of Bates numbers.

Why?

Because the Bates numbers were added as text overlays to the pre-existing image-only PDF files.  When the processing software viewed the file, it found that there was extractable text, so it extracted that text instead of OCRing the PDF file.  In effect, adding the Bates numbers as text overlays to the image-only PDF rendered it as no longer an image-only PDF.  Therefore, the content portion of the text wasn’t captured, so it wasn’t available for indexing and searching.  These documents were essentially rendered non-searchable even after processing.

How did this happen?  Likely through Adobe Acrobat’s Bates Numbering functionality, which is available on later versions of Acrobat (version 8 and higher).  It does exactly that – applies a text overlay Bates number to each page of the document.  Once that happens, eDiscovery processing software applications will not perform OCR on the image-only PDF.

What can you do about it?  If you haven’t applied Bates numbers on the files yet (or have a backup of the files before they were applied – highly recommended) and they haven’t been produced, you should process the files before putting Bates numbers on the images to ensure that you capture the most text available.  And, if opposing counsel will be producing any image-only PDF files, you will want to request the text as well (along with a load file) so that you can maximize your ability to search their production (of course, your first choice should be to receive native format productions whenever possible – here’s a link to an excellent guide on that subject).

If the Bates numbers are already applied and you don’t have a backup of the files without the Bates numbers (oops!) you’re faced with additional processing charges to convert them to TIFF and perform OCR of the text AND the Bates number, a totally unnecessary charge if you plan ahead.

So, what do you think?  Have you dealt with image-only PDF files with text overlaid Bates numbers?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

How Mature is Your Organization in Handling eDiscovery? – eDiscovery Best Practices

A new self-assessment resource from EDRM helps you answer that question.

A few days ago, EDRM announced the release of the EDRM eDiscovery Maturity Self-Assessment Test (eMSAT-1), the “first self-assessment resource to help organizations measure their eDiscovery maturity” (according to their press release linked here).

As stated in the press release, eMSAT-1 is a downloadable Excel workbook containing 25 worksheets (actually 27 worksheets when you count the Summary sheet and the List sheet of valid choices at the end) organized into seven sections covering various aspects of the e-discovery process. Complete the worksheets and the assessment results are displayed in summary form at the beginning of the spreadsheet.  eMSAT-1 is the first of several resources and tools being developed by the EDRM Metrics group, led by Clark and Dera Nevin, with assistance from a diverse collection of industry professionals, as part of an ambitious Maturity Model project.

The seven sections covered by the workbook are:

  1. General Information Governance: Contains ten questions to answer regarding your organization’s handling of information governance.
  2. Data Identification, Preservation & Collection: Contains five questions to answer regarding your organization’s handling of these “left side” phases.
  3. Data Processing & Hosting: Contains three questions to answer regarding your organization’s handling of processing, early data assessment and hosting.
  4. Data Review & Analysis: Contains two questions to answer regarding your organization’s handling of search and review.
  5. Data Production: Contains two questions to answer regarding your organization’s handling of production and protecting privileged information.
  6. Personnel & Support: Contains two questions to answer regarding your organization’s hiring, training and procurement processes.
  7. Project Conclusion: Contains one question to answer regarding your organization’s processes for managing data once a matter has concluded.

Each question is a separate sheet, with five answers ranked from 1 to 5 to reflect your organization’s maturity in that area (with descriptions to associate with each level of maturity).  Default value of 1 for each question.  The five answers are:

  • 1: No Process, Reactive
  • 2: Fragmented Process
  • 3: Standardized Process, Not Enforced
  • 4: Standardized Process, Enforced
  • 5: Actively Managed Process, Proactive

Once you answer all the questions, the Summary sheet shows your overall average, as well as your average for each section.  It’s an easy workbook to use with input areas defined by cells in yellow.  The whole workbook is editable, so perhaps the next edition could lock down the calculated only cells.  Nonetheless, the workbook is intuitive and provides a nice exercise for an organization to grade their level of eDiscovery maturity.

You can download a copy of the eMSAT-1 Excel workbook from here, as well as get more information on how to use it (the page also describes how to provide feedback to make the next iterations even better).

The EDRM Maturity Model Self-Assessment Test is the fourth release in recent months by the EDRM Metrics team. In June 2013, the new Metrics Model was released, in November 2013 a supporting glossary of terms for the Metrics Model was published and in November 2013 the EDRM Budget Calculators project kicked off (with four calculators covered by us here, here, here and here).  They’ve been busy.

So, what do you think?  How mature is your organization in handling eDiscovery?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Good Processing Requires a Sound Process – Best of eDiscovery Daily

Home at last!  Today, we are recovering from our trip, after arriving back home one day late and without our luggage.  Satan, thy name is Lufthansa!  Anyway, for these past two weeks except for Jane Gennarelli’s Throwback Thursday series, we have been re-publishing some of our more popular and frequently referenced posts.  Today’s post is a topic that comes up often with our clients.  Enjoy!  New posts next week!

As we discussed Wednesday, working with electronic files in a review tool is NOT just simply a matter of loading the files and getting started.  Electronic files are diverse and can represent a whole collection of issues to address in order to process them for loading.  To address those issues effectively, processing requires a sound process.

eDiscovery providers like (shameless plus warning!) CloudNine Discovery process electronic files regularly to enable their clients to work with those files during review and production.  As a result, we are aware of some of the information that must be provided by the client to ensure that the resulting processed data meets their needs and have created an EDD processing spec sheet to gather that information before processing.  Examples of information we collect from our clients:

  • Do you need de-duplication?  If so, should it performed at the case or the custodian level?
  • Should Outlook emails be extracted in MSG or HTM format?
  • What time zone should we use for email extraction?  Typically, it’s the local time zone of the client or Greenwich Mean Time (GMT).  If you don’t think that matters, consider this example.
  • Should we perform Optical Character Recognition (OCR) for image-only files that don’t have corresponding text?  If we don’t OCR those files, these could be responsive files that are missed during searching.
  • If any password-protected files are encountered, should we attempt to crack those passwords or log them as exception files?
  • Should the collection be culled based on a responsive date range?
  • Should the collection be culled based on key terms?

Those are some general examples for native processing.  If the client requests creation of image files (many still do, despite the well documented advantages of native files), there are a number of additional questions we ask regarding the image processing.  Some examples:

  • Generate as single-page TIFF, multi-page TIFF, text-searchable PDF or non text-searchable PDF?
  • Should color images be created when appropriate?
  • Should we generate placeholder images for unsupported or corrupt files that cannot be repaired?
  • Should we create images of Excel files?  If so, we proceed to ask a series of questions about formatting preferences, including orientation (portrait or landscape), scaling options (auto-size columns or fit to page), printing gridlines, printing hidden rows/columns/sheets, etc.
  • Should we endorse the images?  If so, how?

Those are just some examples.  Questions about print format options for Excel, Word and PowerPoint take up almost a full page by themselves – there are a lot of formatting options for those files and we identify default parameters that we typically use.  Don’t get me started.

We also ask questions about load file generation (if the data is not being loaded into our own review tool, OnDemand®), including what load file format is preferred and parameters associated with the desired load file format.

This isn’t a comprehensive list of questions we ask, just a sample to illustrate how many decisions must be made to effectively process electronic data.  Processing data is not just a matter of feeding native electronic files into the processing tool and generating results, it requires a sound process to ensure that the resulting output will meet the needs of the case.

So, what do you think?  How do you handle processing of electronic files?  Please share any comments you might have or if you’d like to know more about a particular topic.

P.S. – No hamsters were harmed in the making of this blog post.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

The Files are Already Electronic, How Hard Can They Be to Load? – Best of eDiscovery Daily

Come fly with me!  Today we are winding our way back home from Paris, by way of Frankfurt.  For the next two weeks except for Jane Gennarelli’s Throwback Thursday series, we will be re-publishing some of our more popular and frequently referenced posts.  Today’s post is a topic that relates to a question that I get asked often.  Enjoy!

Since hard copy discovery became electronic discovery, I’ve worked with a number of clients who expect that working with electronic files in a review tool is simply a matter of loading the files and getting started.  Unfortunately, it’s not that simple!

Back when most discovery was paper based, the usefulness of the documents was understandably limited.  Documents were paper and they all required conversion to image to be viewed electronically, optical character recognition (OCR) to capture their text (though not 100% accurately) and coding (i.e., data entry) to capture key data elements (e.g., author, recipient, subject, document date, document type, names mentioned, etc.).  It was a problem, but it was a consistent problem – all documents needed the same treatment to make them searchable and usable electronically.

Though electronic files are already electronic, that doesn’t mean that they’re ready for review as is.  They don’t just represent one problem, they can represent a whole collection of problems.  For example:

These are just a few examples of why working with electronic files for review isn’t necessarily straightforward.  Of course, when processed correctly, electronic files include considerable metadata that provides useful information about how and when the files were created and used, and by whom.  They’re way more useful than paper documents.  So, it’s still preferable to work with electronic files instead of hard copy files whenever they are available.  But, despite what you might think, that doesn’t make them ready to review as is.

So, what do you think?  Have you encountered difficulties or challenges when processing electronic files?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Our 1,000th Post! – eDiscovery Milestones

When we launched nearly four years ago on September 20, 2010, our goal was to be a daily resource for eDiscovery news and analysis.  Now, after doing so each business day (except for one), I’m happy to announce that today is our 1,000th post on eDiscovery Daily!

We’ve covered the gamut in eDiscovery, from case law to industry trends to best practices.  Here are some of the categories that we’ve covered and the number of posts (to date) for each:

We’ve also covered every phase of the EDRM (177) life cycle, including:

Every post we have published is still available on the site for your reference, which has made eDiscovery Daily into quite a knowledgebase!  We’re quite proud of that.

Comparing our first three months of existence to now, we have seen traffic on our site grow an amazing 474%!  Our subscriber base has more than tripled in the last three years!  We want to take this time to thank you, our readers and subcribers, for making that happen.  Thanks for making the eDiscoveryDaily blog a regular resource for your eDiscovery news and analysis!  We really appreciate the support!

We also want to thank the blogs and publications that have linked to our posts and raised our public awareness, including Pinhawk, Ride the Lightning, Litigation Support Guru, Complex Discovery, Bryan University, The Electronic Discovery Reading Room, Litigation Support Today, Alltop, ABA Journal, Litigation Support Blog.com, InfoGovernance Engagement Area, EDD Blog Online, eDiscovery Journal, e-Discovery Team ® and any other publication that has picked up at least one of our posts for reference (sorry if I missed any!).  We really appreciate it!

I also want to extend a special thanks to Jane Gennarelli, who has provided some serial topics, ranging from project management to coordinating review teams to what litigation support and discovery used to be like back in the 80’s (to which some of us “old timers” can relate).  Her contributions are always well received and appreciated by the readers – and also especially by me, since I get a day off!

We always end each post with a request: “Please share any comments you might have or if you’d like to know more about a particular topic.”  And, we mean it.  We want to cover the topics you want to hear about, so please let us know.

Tomorrow, we’ll be back with a new, original post.  In the meantime, feel free to click on any of the links above and peruse some of our 999 previous posts.  Now is your chance to catch up!  😉

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

It’s Friday at 5 and I Need Data Processed to Review this Weekend – eDiscovery Humor

We’ve referenced Ralph Losey’s excellent e-Discovery Team® blog several times before on this blog – it’s a great read and you won’t find a blog that gets more in depth than his does (he has also been gracious enough to participate in our thought leader interview series for the last three years).  And, as Ralph has demonstrated before, he has a sense of humor when it comes to electronic discovery.

In his latest post, Are You The Lit Support Tech?, Ralph takes a humorous look at “what it is like on a Friday afternoon in the Litigation Support Departments of most law firms”.  Or so it seems sometime.  Like before, Ralph used XtraNormal to make the video.  XtraNormal enables you to make an animated movie by selecting your animated “actors”, type or record your dialogue, and select a background.  The “actors” sound a bit robotic if you type the dialogue, but that just adds to the humor as the pronunciations and inflections are rather humorous.

Anyway, the video involves a law firm partner coming to the lit support tech on a Friday afternoon and asking for help to process data for ten custodians so that he can review over the weekend as the production is due Monday.  “When did you receive the request?”, asks the tech.  “30 days ago”, says the partner, “Why?”.  “No reason”, says the tech.

The video continues with the partner telling the tech not to worry “it’s only 15 gigabytes…not such a big number”.  When the tech says that it’s over a million pages and he will have to process it and load it into their review platform, the partner says “I don’t have time for all the processing and stuff, just print it out and load it in my car.”

OK, so part of the humor is that it’s a bit farfetched (hopefully).  Ralph notes that because he no longer has to supervise a litigation support department (because Jackson Lewis outsources all of its nonlegal electronic data discovery work), his “Friday afternoons are much nicer”.

It’s the vendor that has to deal with these last minute requests.  At CloudNine Discovery, we can relate to the lit support tech who receives 15 gigabytes (or even more) on a Friday afternoon to process for weekend review – we get those types of requests more often than you think and our staff often works late Fridays to get the client’s data ready.  It goes with the territory.  So, we don’t make big plans on Friday night so that you can enjoy yours!

So, what do you think?  Have you had to deal with last minute eDiscovery requests?  If so, how do you handle them?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.