Essays

One of the things we do as analysts is take inquiries from readers, typically either in a half hour call or via an email response. Recently, a good inquiry came in, but there was no contact information to send an answer to, so I thought it would be a good idea to answer it here (with the hope that the answer gets to the person that had the question). The question read, “If we have a corporate email solution that strips attachments from emails and replaces them with download links, what are our e-discovery responsibilities? Do we need to be able to produce the attachment, or just the email with the links?”

As eDiscovery transitions from fire drill to business process, corporations and law firms are struggling to measure and manage the time and cost associated with the EDRM lifecycle. Up to this point, we have only had ONE standardized billing code in the ABA’s Uniform Task-Based Management System (UTBMS) litigation codes, L390 Other Discovery to be exact. Last year, the Legal Electronic Data Exchange Standard Oversight Committee (LEDES) reached out to the EDRM Metrics Project to participate in the formation of a revised set of new L600 series UTBMS eDiscovery billing codes. The draft code set has been posted to the LEDES site for comments until May 2nd. I highly encourage you to review the new codes and to contribute your perspective.

We are pleased to announce that independent eDiscovery counsel and consultant Kevin Esposito will now be contributing blogs as an eDJ Expert. For those of you who have enjoyed listening to his unique presentation style at conferences, EDRM Committees, Sedona and other eDiscovery gatherings, we know that you will continue to enjoy his direct and uncompromising perspective. Kevin brings with him over 12 years of eDiscovery experience, having managed the litigation support and IT infrastructure operations within global Fortune 50 corporations. While on the corporate side of the house, he became well known for his technology leadership in the logistics world and his efforts at redefining litigation support processes in the pharmaceutical industry. For the past five years, however, clients in those areas as well as the manufacturing, financial services and entertainment sectors have been quietly relying on his operational and legal guidance as an independent discovery counsel. He has forged a unique niche by helping companies and law firms to meet their joint discovery obligations by combining the talents of the client, support vendors large and small and the judicious application of many of the popular litigation support tools and technologies. He and his team have learned how to help companies safely and successfully negotiate the eDiscovery minefield through their daily contact with vendors, staffing groups and technology suppliers. He will assist our eDJ readers by providing a pragmatic view of issues large and small, both legal and personal. I have had the pleasure of partnering with Kevin on consulting engagements covering litigation system audits, RFP generation and management and eDiscovery/Records Retention lifecycle projects. He brings both operational experience and a slightly different personal focus to our blogs and research papers. Kevin can be reached here at Kevin@ediscoveryjournal.com. We hope you that you enjoy his contributions.

One of the challenges in the eDiscovery market is the need for organizations to keep best practices to themselves. There are few organizations willing to publicly share the details of eDiscovery programs. True, one of the reasons for this is the fact that most eDiscovery programs are very immature. But, the primary reason is risk control – there is very little benefit to going public with eDiscovery practices and a lot of downside (e.g. losing the ability to argue undue burden because the whole world knows about your search capabilities). Thus, I was very happy when I found someone from a top telecomm company willing to share some lessons learned (while I can’t share name or company name, I can share some very interesting knowledge nuggets)

Everyone knows how to send an email and Blind Carbon Copy (BCC) certain recipients separately from your public TO/CC recipients. I responded to a recent question on the Yahoo! LitSupport list regarding the best practices for production of email with BCC information. My response kicked off several offline questions about the actual nature of BCC information, preservation of such information and deduplication of email with/without BCC recipients. I have had to wrestle with this from an audit and a product development perspective several times, but it seems worthwhile to try to write a decent overview of BCC and eDiscovery.

Greetings to all of the readers of the eDiscoveryJournal. I’m pleased to join you as the newest correspondent and hope that you will find that what l share in this forum is useful. Now that I’m here, I’m sure some of you are wondering, “Just what is an independent consultant going to share?" Some may suspect that there will be a dry recitation of product reviews and hardware specs. Some may worry that I’m going to belabor yet again subjects such as “Are instant messages ‘records’?” And some that have heard me speak in public worry that I might just take off all the safeties and satirize what I see out there in the eDiscovery business world. While the last is the most tempting, I personally hate when the Internet is used to push personal agendas. No dear friends, I intend to do the practical thing and provide you with the “One Thousand Foot View”.

I recently finished a research paper that takes an overview of Enterprise Search for Discovery. My intent was to aggregate, organize and condense corporate client discussions around this area over the last year. Enterprise search and preservation collection platforms are the second most frequent technology RFP engagement for my corporate clients after archiving systems. The technology providers have many different approaches, architectures and features that can confuse the prospective buyer. After having the same discussion so many times, I decided to put together a low cost ($29) overview report to at least define the options, potential benefits, costs and things to consider before investing in enterprise search. Enterprise search tends to fall into two main indexing camps, selective vs. enterprise wide. One element from the report is the potential index size, as indexes like to live on Tier 1 class storage (SAN, Direct Attached or other top class storage).

After watching the IBM Watson debut on Jeopardy, I got to thinking more and more about computer intelligence. I’ve been watching the content analytics space for a long time and have seen up close both the potential for analytics to change the world and the skepticism with which many humans view analytics. When I began covering eDiscovery, it seemed to me that there was finally a market in which content analytics could make a real impact and find some traction. This is especially true in Early Case Assessment (ECA).

I cannot count the times I have heard something along the lines of, “I just want to wave a magic wand and make all those bloody PSTs go away.” I heard it again just last week. At least this time the speaker was well along the actual process of migrating the email so that the PSTs could be disabled and done away with. You could use an email archive platform, Sharepoint, ECM system or even Exchange 2010 (just watch out for the storage balloon!) to manage and expire email designated as corporate records. Pick your poison, but you still have to deal with the years of accumulated email that your users have stashed in all those handy Personal Stores (.PST and .OST files). Many categorization technologies have promised to magically designate items as records and cull out all the dross. I have yet to see one deliver on real, heterogeneous legacy email outside of very structured environments where users already have to manage communications and documents. Typical corporate goals include the defensible destruction of non-essential email, central management/search of designated records and minimization of eDiscovery/infrastructure costs. I wanted to share some of my lessons learned from past PST elimination projects, both successful and the rescue attempts.

A recent New York Times article gave eDiscovery some primetime coverage. The focus of the article was more macro-level: given the software tools to automate aspects of document review, are we ultimately creating less high-paying jobs for lawyers? As expected of a mainstream press article on eDiscovery, only broad strokes were sketched. The article does propose a very good and timely question. The elimination of high-paying jobs could have a potentially devastating impact on our economy. From my perspective, what was missing from the article was the potential for software tools that replace document reviewers to create another wave of high-paying jobs (that are different because they aren’t “lawyer” jobs).