Industry Trends

eDiscovery Trends: Welcome to ILTA 2014!

 

The International Legal Technology Association (ILTA) annual educational conference of 2014 kicked off yesterday with several networking events, and begins in earnest today with the first day of sessions.  eDiscoveryDaily will be reporting this week about the latest eDiscovery trends being discussed at the show.  Over the next four days, we will provide a description each day of some of the sessions related to eDiscovery to give you a sense of the topics being covered.

If you’re in the Nashville area, come check out the show – there are a number of sessions available and over 190(!) exhibitors providing information on their products and services.  Perform a “find” on today’s ILTA conference schedule for “discovery” or “information governance” and you’ll get 8 sessions with hits.  So, there is plenty to talk about!  Sessions in the main conference tracks include:

10:45 AM – 12:00 PM:

Law Department Operations Roundtable (Law Department Day)

Description: Law departments experience myriad issues unrelated to e-discovery. Let's get 'em out on the table! We'll discuss topics that interest attendees and hear from those who have tackled these issues.

Speaker is: Thomas Morrissey – Purdue Pharma L.P.

11:00 AM – 12:00 PM:

A Need for Speed: Leveraging Analytics in Document Review

Description: Dwindling are the days of straight linear reviews as the volume and complexity of data involved in e-discovery make it nearly impossible to deliver timely, error-free services. Our experienced panelists will describe and demonstrate how they have leveraged various strategies and advanced analytics to achieve accurate, timely and defensible results.

Speakers are: Greg R. Chan – Bingham McCutchen LLP; Michael Quartararo – Stroock & Stroock & Lavan LLP; Joy Holley – Bryan Cave, LLP.

12:00 PM – 1:30 PM:

Diving Deep Into E-Discovery: Law Department Roundtable (Law Department Day)

Description: For many law departments, significant portions of the budget and resources are allocated to e-discovery. Participate in this roundtable as we discuss e-discovery challenges in the short- to mid-term, e-discovery best practices, collaboration with vendors and law firms, and identification of high-performing providers and e-discovery tools and systems.

Speakers are: Eric Lieber – Toyota Motor Sales; Julie M Richer – American Electric Power Legal Department.

1:00 PM – 2:00 PM:

What Makes Up ESI Protocols? (Part I)

Description: A "Meet and Confer" in three acts! This panel will offer drama, intrigue and a good time for all. Watch two parties prepare for and then engage in a Meet and Confer session involving common e-discovery issues. Go behind the scenes as each party strategizes and formulates their "position," then observe as they work to put themselves and their clients in the best position possible. Remaining disputes will be argued in front of the "court."

Speakers are: Patrick L. Oot – Shook, Hardy & Bacon L.L.P.; Bryon Bratcher – Reed Smith LLP; Andrew J Peck – US District Court Southern District of New York; Steven L. Clark – Lathrop & Gage LLP; Candi Smith – Winston & Strawn LLP; Joy Holley – Bryan Cave, LLP; Craig Ball – Craig D. Ball, P.C.; Dera Jardine Nevin – Re:Discovery Law PC.

Build Enterprise Information Governance from the Ground Up

Description: Enterprise information governance programs are often as complex as the problems they intend to solve, incorporating governance needs, requirements from various internal and external stakeholders, and tight budgets. Here we’ll walk through best practices any organization can use to kick-start an IG program and make quick progress. We’ll discuss topics like assessing the current situation and capabilities, prioritizing risks and opportunities, gaining support from all stakeholders for an IG framework, and simple ways to start.

Speakers are: Rudy Moliere – Morgan, Lewis & Bockius, L.L.P.; Eric Mosca – InOutsource; Dana C. Moore – Vedder Price P.C.; Bennett Borden – Drinker Biddle & Reath LLP.

2:30 PM – 3:30 PM:

Predictive Analytics: Email Management Magic?

Description: Email management — managing mailbox size, archiving and retention — remains at the top of the list of email challenges identified by firms in the ILTA Technology Survey. A diverse panel of vendor and information governance experts will focus on specific predictive analytics applications and technologies that are available that could tackle email management. How do the solutions work, and what might they require from technical, cost and risk standpoints? Can predictive analytics perform email management magic?

Speakers are: Neil Etheridge – Recommind, Inc.; Avi Elkoni – Equivio; Jason R Baron – Drinker Biddle & Reath LLP; Sandra Serkes – Valora Technologies, Inc.; Mark Olson – Data Skill, Inc.

3:15 PM – 4:15 PM:

Services and Applications: Jump-Start the Vetting Process (Law Department Day)

Description: Join your law department peers for an interactive discussion about matter management, e-discovery and legal holds. In the unique format of "mini-panels," participants will engage in discussions on each topic in three 15-minute breakout sessions. This will allow for more intimate group discussions. The types of questions and topics to be vetted in each mini-panel include various software solutions and how your organization utilizes them, processes and procedures, what is working best for you and key criteria for selecting the right fit for your company.

Speakers are: Glenn O'Brien – Massachusetts Mutual Life Insurance Company; Amie Dutey – Nationwide Mutual Insurance; Anthea Cooper – Nationwide Mutual Insurance; Donald Knight – PNC Bank Legal Department; Martin Susec – Nationwide Mutual Insurance.

4:00 PM – 5:00 PM:

What Makes Up ESI Protocols? (Part II)

Description: This is part two of our "Meet and Confer" in three acts! This panel will offer drama, intrigue and a good time for all. Watch two parties prepare for and then engage in a Meet and Confer session involving common e-discovery issues. Go behind the scenes as each party strategizes and formulates their "position," then observe as they work to put themselves and their clients in the best position possible. Remaining disputes will be argued in front of the "court."

Speakers are: Patrick L. Oot – Shook, Hardy & Bacon L.L.P.; Bryon Bratcher – Reed Smith LLP; Andrew J Peck – US District Court Southern District of New York; Steven L. Clark – Lathrop & Gage LLP; Candi Smith – Winston & Strawn LLP; Joy Holley – Bryan Cave, LLP; Craig Ball – Craig D. Ball, P.C.; Dera Jardine Nevin – Re:Discovery Law PC.

For a complete listing of all sessions at the conference, click here.

So, what do you think?  Are you planning to attend ILTA this year?  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.

Nearly Two Thirds of ILTA Attendees are from Large Firms – eDiscovery Trends

 

One of the biggest legal technology shows of the year, the International Legal Technology Association (ILTA) annual educational conference for 2014 will take place next week at the Gaylord Opryland in Nashville (August 17 thru August 21).  eDiscoveryDaily will be reporting next week about the latest eDiscovery trends being discussed at the show.  According to InsideLegal.com, almost two thirds of the firm attendees will come from firms with more than 200 attorneys.

As noted by their graphic (available here), 62% of the attendees (based on conference pre-registrants as of August 12) will come from firms with more than 200 attorneys.  Here is the breakdown:

  • 1-50 Attorneys: 13% of attendees;
  • 51-100 Attorneys: 11% of attendees;
  • 101-200 Attorneys: 14% of attendees;
  • 201-400 Attorneys: 18% of attendees;
  • 401-1,000 Attorneys: 31% of attendees;
  • 1,001+ Attorneys: 13% of attendees.

InsideLegal also provides a breakdown of registrants by country – not surprisingly, 1,345 out of 1,466 attendees (nearly 92%) as of July 29 are from the US.

We will identify the sessions each day that relate to eDiscovery and Information Governance, so stay tuned!

So, what do you think?  Are you attending the ILTA conference this year?  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.

eDiscovery Blog Throwback Thursdays – How Databases Were Built, Circa Early 1980s, Part 1

 

In the late 1970s and early 1980s, very few law firms had internal litigation support resources:  firms did not have litigation support staff or technology.  In 1985, I was offered a litigation support position at a major New York City law firm (which I didn’t accept),,, that’s about when large firms began developing internal litigation support capabilities.  Up until then, most litigation teams relied on vendor services and tools, and more often than not litigation team attorneys were directly involved in working with vendors to design and build databases. In 1980 I took a project management position with a vendor, responsible for overseeing database-building projects. In the next few blog posts, I’m going to describe a typical project and how things worked.

The Vendor Selection Process: This of course was not a ‘step in the project’ – it was part of the sales process. It’s worth mentioning here though, because this was a very big deal, on every project. Because databases were only built for the huge, bet-your-company cases, every project was a big project. For any given project, a vendor would receive a Request for Proposal, which usually required a voluminous, detailed response.

Database Design and Planning: We often spent days in meetings with attorneys designing and planning a database.  Back then, full text wasn’t included in databases and images weren’t included in databases.  That meant that the information that was “coded” for a document was very, very important — It was the only thing in the database.  We needed to learn about a case, learn about the documents, and find out how the attorneys expected to use the documents – this was necessary so that we could advise litigation teams on a coding scheme that would meet their needs.  Remember, this was back before PCs. Back before the Internet. Back before Google. Business people — as a rule — did not understand databases or searching. We, as vendors and consultants needed to be educators, and we needed to advise our attorney clients and recommend – on a case-by-case basis — a design that would meet their needs.

Project Preparation: Sometimes we did projects at our vendor facility, and other times clients requested that we establish a ‘coding operation’ at their site. In either case, we needed to assemble a team of coders. These were usually temporary employees hired for a specific project. Since all the cases we did were big cases, the teams were often substantial. It wasn’t at all unusual to start with a team of 50 or more. The largest project I worked on used a coding team of over 1,000. Of course there were other preparation tasks, but assembling the coding team was the most time consuming. When ever possible, we used people from prior projects, but inevitably, project managers spent a lot of time interviewing candidates for coding positions on every new project.

In next week’s post, we’ll talk more about how a coding project worked.

Please let us know if there are eDiscovery topics you’d like to see us cover in eDiscoveryDaily.

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.

Improving your eDiscovery Vocabulary is as Easy as 123 – eDiscovery Best Practices

Want to be better equipped to speak the “lingo” of eDiscovery and understand what you’re saying?  Here’s a glossary that can help.

As provided via the JDSupra Business Advisor site, Electronic Discovery: Glossary of 123 Commonly Used Terms, provided by Seattle law firm Lane Powell PC, is a glossary of 123 commonly used terms to help you navigate the world of Electronic Discovery.  For those of us who have been in the industry for years, call them Terms of Endearment!

From Active Data to Zip, the glossary defines 123 total terms related to eDiscovery as well as technology in general.  You get discovery terms defined ranging from Bates Number and Chain of Custody to Redaction and Spoliation and technology terms from Cache (pronounced “cash”) and Compression to Unallocated Space and VPN (Virtual Private Network).

You can review the terms from the window on the JD Supra site or download the PDF document for reference purposes.  This list comes in handy for anyone who may need a better understanding of eDiscovery and technology or simply needs a refresher on certain terms.

I did not see definitions for all of the EDRM phases (e.g., no definitions for Identification, Collection, Analysis, Processing or Presentation) and some other terms that might be useful to define (e.g., Searching), so maybe they can eventually issue a supplemented version that has 144 defined terms.  Now, that’s gross!

By the way, today is the last day that you can nominate your favorite law blog in the ABA Journal 8th Annual Blawg 100.  Get your nominations in by 5:00pm!

If you have enjoyed reading eDiscovery Daily over the past year and found our blog to be informative, we would love to be recognized!  Feel free to click on the link here to nominate us!  We appreciate the consideration!

There are other excellent legal technology blogs out there.  Click here for our previous post which lists a few of our favorites.

So, what do you think?  Do you speak fluent 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.

eDiscovery Throwback Thursdays – The Way We Worked, circa 1980

 

In the late 1970s and early 1980s, the business world looked very different than it does today, and the field of litigation support looked very different than it does today.  Let me paint a picture for you…

  • Mainframe and mini computers were in use in many large and some mid-sized businesses.  They were, however, ‘back-office’ functions.  You didn’t see computers on office desks.  A few desks did have computer terminals, but not many. Disk drives with a capacity measured in the low hundreds of megabytes were the size of washing machines.
  • Although precursors to the internet were in early stages, only ‘computer geeks’ knew about it (and there weren’t that many computer geeks).
  • For the most part, law firms – even very large firms – did not have internal litigation support database tools.  Litigation databases were stored and accessed on the mainframe computers of service providers, which offered ‘time-share’ services.  Typically, those service providers charged a monthly storage fee based on the size of a database, and a per-hour charge for usage.
  • The timeshare databases were accessed with computer terminals – also called ‘dumb’ terminals.  Those terminals did not have screens.  Rather, you inserted a roll of thermal paper, which was ‘spit-out’ with search results (you always needed an ample supply of paper rolls so you weren’t in a bind when the paper ran out during a search session).  You hooked a telephone receiver to an acoustic coupler on the terminal, dialed the computer’s phone number, waited for the high-pitched, scratchy screech that indicated a successful connection, and then queried the database.
  • Databases consisted primarily of “coded” information like dates, authors, recipients, titles, and so on.  Many databases included ‘subject coding’.  There were no images included in litigation databases back then, and including full text didn’t get legs in the litigation support world until the mid to late 1980s.
  • Database search engines did not provide WYSIWYG interfaces or menu options.  You entered precise search commands like “Find Author=Smith-JA and Type=Letter”.
  • Most law firms did not have litigation support professionals on staff.  That work was handled by service providers.
  • Those service providers offered, for the most part, document coding services.  There were only a handful of service providers, and those providers offered services nationally.  When I took my first vendor job (in 1980), we had 5 main competitors and found ourselves all bidding on the same jobs.  The litigation support community was small, and we pretty much all knew each other.
  • No one, and I mean NO ONE, outside of our world understood what we did for a living.  On more than one occasion I heard my mother proudly explaining to a friend that I was a computer programmer.

And that’s how it was, back when I first started in this field.  In the posts to come, I’m going to give more detail on some of these points as we move on to discuss how databases were built, and how searching / retrieval worked.

Please let us know if there are eDiscovery topics you’d like to see us cover in eDiscoveryDaily.

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.

eDiscovery Professional Profile: Do you know Cheryl Garner?

 

Cheryl Garner is the Practice Support Manager at Manning & Kass, Ellrod, Ramirez, Trester LLP – a 150 attorney law firm with six offices in the U.S. Cheryl is located in the firm’s main office in Los Angeles, but has firm-wide responsibility. She joined the firm in December 2012, after a long and diverse career in the legal field.

As Practice Support Manager, Cheryl is responsible for litigation support, paralegal staff, the Docket Department, and the Workers Compensation Hearing Representatives. She spends most of her time coordinating the work of those departments, reaching out to attorneys to ensure they have the support they need, marketing the services of the departments for which she is responsible, and educating attorneys regarding best practices and making optimal use of the technology available to them.  She describes herself as a ‘Jack of all trades’ and often steps in with rolled-up sleeves to complete tasks alongside team members. She also directly handles firm-wide litigation support and eDiscovery, working closely with service providers that process data and provide hosting platforms for large cases.

Cheryl’s first legal position was with the US Attorneys office in Chicago.  She was a member of a word processing pool for the civil and criminal teams. From there she went to work for the American Bar Association as a word processing operator, and later worked in law firms as a legal secretary and word processing operator.  As technology advanced, Cheryl recognized that opportunities in word processing would diminish, and she developed a plan for her future.  While working full-time, she completed her undergraduate studies in 2000 and in 2002 she completed an ABA-approved paralegal program.  Armed with a background that included hands-on government and law firm experience, as well as paralegal and technology experience, career opportunities broadened.  Up until 2008 she worked for large law firms providing secretarial, paralegal, technology, and trial support.  In 2008 when she moved to a smaller firm, she soon recognized it was the perfect fit for her at that stage of her career. She believes that the experience she got at the smaller firms after working primarily in larger firms has been invaluable.

In 2012, Cheryl joined Manning & Kass as Practice Support Manager, a recently created position.  The position was still in its infancy when Cheryl came on board, and she saw this as a logical progression in her career.  Cheryl enjoys her work because it incorporates – and requires – the skills she has honed and the interaction she enjoys.  The firm’s structure, having paralegals report to Practice Support, increases opportunities to introduce litigation technology to the litigation teams.  It’s a model that works well for Cheryl.

When asked about her greatest professional accomplishment, Cheryl quickly answered “Getting to where I am now in my career”.  Through hard work, foresight of the use of law firm technology, and education, Cheryl planned and crafted a career that she is proud of, one that she is good at, and one that she thoroughly enjoys.

Throughout her career, Cheryl has been active in professional organizations. While still a paralegal student, Cheryl joined the Los Angeles Paralegal Association (LAPA). Later, she sat on LAPA’s Board of Directors and was Chair of the Litigation Committee.  She is still a member today.  She is also a member of NALA (National Association of Legal Assistants), and recently earned the Advanced Certified Paralegal (ACP) designation in discovery.  She is a member of ACEDS (Association of Certified E-Discovery Specialists) and plans to sit for the CEDS certification exam in the near future.

Cheryl is also an instructor in the technology track of the ABA-approved paralegal program at California State University Los Angeles (CSULA).  Since 2011 she has taught the introductory course Law Office Technology, and more recently, Trial Technology.  She will teach Applied Technology in the Fall of 2014. Cheryl enjoys teaching because it offers her an opportunity to equip paralegals entering the field with the legal technology foundation they will need to succeed as legal professionals.

Cheryl is originally from Chicago, Illinois and started her professional career there.  She moved to Los Angeles 22 years ago with her son, who today also works in the legal industry.  While her work at Manning & Kass and teaching at CSULA take up most of her time, Cheryl finds time to enjoy ‘Chicago Style Stepping’, an urban dance that originated in Chicago and is similar in movements to’ West Coast Swing’ and Lindy Hop.  Cheryl travels to different cities to attend dancing events.  There’s a lot of camaraderie among attendees from different cities, but the dance has recently re-emerged in popularity as a competitive dance, providing attendees an opportunity to showcase stylings from their region of the country.  Although Cheryl hasn’t competed yet, she keeps the possibility open for the future.  Jazz and other styles of music are important to Cheryl and she often attends local jazz concerts and art events around Los Angles.  She’s currently looking forward to a cruise she’s planning with her sister, to an island ‘to be determined’.

Please let us know if there are eDiscovery topics you’d like to see us cover in eDiscoveryDaily.

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.

August Case Law Pop Quiz Answers! – eDiscovery Case Law

Yesterday, we gave you a pop quiz for the eDiscovery case law that we’ve covered in the past three months. If you’re reading the blog each day, these questions should be easy! Let’s see how you did. Here are the answers.

1.  In which case was the plaintiff was ordered to produce photos of herself that were posted to Facebook?:

A. Castillon v. Corrections Corporation of America, Inc.

B. In Cactus Drilling Co. v. Nat’l Union Fire Ins. Co.

C. Forman v. Henkin

D. None of the above

2.  In which case were sanctions imposed, even though no spoliation of evidence ultimately occurred?:

A. EEOC v. SVT, LLC

B. Procaps S.A. v. Patheon Inc.

C. Knickerbocker v Corinthian Colleges

D. None of the above

3.  In which case was over $50,000 of eDiscovery costs awarded to the prevailing party disallowed?:

A. Kwan Software Engineering v. Foray Technologies

B. Miller v. York Risk Servs. Grp.

C. United States v. Shabudin

D. In Progressive Cas. Ins. Co. v. Delaney

4.  In what case was one party ordered to continue to share a review database with the opposing party?:

A. Kwan Software Engineering v. Foray Technologies

B. Miller v. York Risk Servs. Grp.

C. United States v. Shabudin

D. In Progressive Cas. Ins. Co. v. Delaney

5.  In which case did the court disallow the plaintiff’s plan for predictive coding?:

A. Kwan Software Engineering v. Foray Technologies

B. Miller v. York Risk Servs. Grp.

C. United States v. Shabudin

D. In Progressive Cas. Ins. Co. v. Delaney

6.  In what case was the defendant’s request for a deposition to review whether the plaintiff had used “appropriate search tools for ESI discovery” denied?:

A. Koninklijke Philips N.V. v. Hunt Control Sys., Inc.

B. Elkharwily v. Mayo Holding Co.

C. Stallings v. City of Johnston City

D. Raines v. College Now Greater Cleveland, Inc.

7.  In which case did the court suggest the parties consider the use of predictive coding?:

A. Chapman v. Hiland Operating, LLC

B. FDIC v. Bowden

C. Downs v. Virginia Health Systems

D. Zeller v. So. Central Emergency Med. Servs. Inc.

8.  How much was Samsung and Quinn Emanuel ordered to pay for their “Patentgate” disclosure of confidential Apple and Nokia agreements?:

A. $1 million

B. $2 million

C. $3 million

D. $10 million

9.  In which case did the court not only reject the plaintiff’s request for sanctions, but issued a summary judgment in favor of the defendant?:

A. Zeller v. So. Central Emergency Med. Servs. Inc.

B. In re Text Messaging Antitrust Litig.

C. Brown v. Tellermate Holdings

D. Brookshire Bros., Ltd. v. Aldridge

10. In which case did the court issue a severe sanction against the defendant for failure to preserve data from cloud provider Salesforce.com?:

A. Zeller v. So. Central Emergency Med. Servs. Inc.

B. In re Text Messaging Antitrust Litig.

C. Brown v. Tellermate Holdings

D. Brookshire Bros., Ltd. v. Aldridge

As always, please let us know if you have questions or comments, or if there are specific topics you’d like to see covered.

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.

August Case Law Pop Quiz! – eDiscovery Case Law

We haven’t conducted a pop quiz in a while, so the “dog days” of summer seems like a good time for it.  This one is customized to the eDiscovery case law that we’ve covered the past three months.  If you’re reading the blog each day, these questions should be easy!  If not, we’ve provided a link to the post with the answer.  We’re that nice.  Test your knowledge!  Tomorrow, we’ll post the answers for those who don’t know and didn’t look them up.

1.  In which case was the plaintiff was ordered to produce photos of herself that were posted to Facebook?:

A. Castillon v. Corrections Corporation of America, Inc.

B. In Cactus Drilling Co. v. Nat’l Union Fire Ins. Co.

C. Forman v. Henkin

D. None of the above

2.  In which case were sanctions imposed, even though no spoliation of evidence ultimately occurred?:

A. EEOC v. SVT, LLC

B. Procaps S.A. v. Patheon Inc.

C. Knickerbocker v Corinthian Colleges

D. None of the above

3.  In which case was over $50,000 of eDiscovery costs awarded to the prevailing party disallowed?:

A. Kwan Software Engineering v. Foray Technologies

B. Miller v. York Risk Servs. Grp.

C. United States v. Shabudin

D. In Progressive Cas. Ins. Co. v. Delaney

4.  In what case was one party ordered to continue to share a review database with the opposing party?:

A. Kwan Software Engineering v. Foray Technologies

B. Miller v. York Risk Servs. Grp.

C. United States v. Shabudin

D. In Progressive Cas. Ins. Co. v. Delaney

5.  In which case did the court disallow the plaintiff’s plan for predictive coding?:

A. Kwan Software Engineering v. Foray Technologies

B. Miller v. York Risk Servs. Grp.

C. United States v. Shabudin

D. In Progressive Cas. Ins. Co. v. Delaney

6.  In what case was the defendant’s request for a deposition to review whether the plaintiff had used “appropriate search tools for ESI discovery” denied?:

A. Koninklijke Philips N.V. v. Hunt Control Sys., Inc.

B. Elkharwily v. Mayo Holding Co.

C. Stallings v. City of Johnston City

D. Raines v. College Now Greater Cleveland, Inc.

7.  In which case did the court suggest the parties consider the use of predictive coding?:

A. Chapman v. Hiland Operating, LLC

B. FDIC v. Bowden

C. Downs v. Virginia Health Systems

D. Zeller v. So. Central Emergency Med. Servs. Inc.

8.  How much was Samsung and Quinn Emanuel ordered to pay for their “Patentgate” disclosure of confidential Apple and Nokia agreements?:

A. $1 million

B. $2 million

C. $3 million

D. $10 million

9.  In which case did the court not only reject the plaintiff’s request for sanctions, but issued a summary judgment in favor of the defendant?:

A. Zeller v. So. Central Emergency Med. Servs. Inc.

B. In re Text Messaging Antitrust Litig.

C. Brown v. Tellermate Holdings

D. Brookshire Bros., Ltd. v. Aldridge

10. In which case did the court issue a severe sanction against the defendant for failure to preserve data from cloud provider Salesforce.com?:

A. Zeller v. So. Central Emergency Med. Servs. Inc.

B. In re Text Messaging Antitrust Litig.

C. Brown v. Tellermate Holdings

D. Brookshire Bros., Ltd. v. Aldridge

As always, please let us know if you have questions or comments, or if there are specific topics you’d like to see covered.

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.

Are Law Firms at an eDiscovery “Watershed”? – eDiscovery Trends

 

Perhaps so, based on the results of one survey.

As reported by Sean Doherty of Law Technology News (Survey: Law Firms Are at E-Discovery 'Watershed'), according to a survey released on July 22, sponsored by RVM Enterprises Inc. and conducted by Ari Kaplan Advisors, law firms are at a “watershed” moment when it comes to creating efficient eDiscovery models for supporting their corporate clients.

As the Introduction to the report stated, “RVM retained Ari Kaplan Advisors to engage 30 senior attorneys at many of the nation’s largest law firms in detailed conversations during the first quarter of 2014 about past, present, and future trends in the legal community.  The findings, based on these interviews, characterize the catalysts transforming the profession in an era of expansive eDiscovery and highlight how organizations are universally pivoting to remain current in their approach to client service.”

Regarding the survey participants, “73% are partners and 27% are senior eDiscovery lawyers. All are members of an eDiscovery group within their firms to varying degrees. 100% recommend eDiscovery tools and vendors to corporate counsel, and also develop and implement eDiscovery processes.”  So, these are people who are certainly eDiscovery advocates.  Here are a few highlights of the findings from the report:

  • 93% of respondents said that client expectations have changed with respect to practice support technology and related costs;
  • 73% of respondents said that their firm has an eDiscovery counsel position (though not all specifically designate their lawyers with that title);
  • 79% of respondents reported that the role of eDiscovery counsel is both an internal resource and an external marketing tool;
  • 57% of respondents stated that they have had a client request that they work with eDiscovery counsel;
  • 93% of respondents reported that a combination of individuals is engaged in the practice support technology and vendor selection process;
  • 97% of respondents outsource some portion of their eDiscovery, with the most common aspect being processing, and
  • 83% of respondents have received a client request to write off eDiscovery costs.

There is quite a bit more to the report, including other stats and specific observations from individual participants, including the challenge to bill for eDiscovery services – “Clients think that eDiscovery services should be part of the operating costs of the firm” was one observation.

Here is a link to a press release from RVM Enterprises announcing the report – the 14 page report, prepared by Ari Kaplan Advisors, is available in PDF format via a link on the press release.  Best of all, the report is FREE.

So, what do you think?  How do those stats compare to experiences in your firm?  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.

eDiscovery Throwback Thursdays – Collecting Documents

 

In 1978, I took my first job in litigation, with the law department of a Fortune 100 corporation headquartered in New York City. I was one of a team assembled to collect responsive documents to be produced in a major antitrust litigation. The documents were located in the corporation’s office and warehouse facilities around the country. While the process of collecting documents varied from case to case, this project was representative of the general approach to collecting documents in large-scale litigation. Let me describe how it worked.

Before travelling to a facility, reviews of custodian files were scheduled, central files to be reviewed were identified, and indices of boxes of archived materials in warehouses were reviewed.  We coordinated with an on-site administrator to ensure that the supplies we needed would be ready (boxes, manila file folders, pads, stickers, markers, etc.), and we made arrangements for a temporary photocopy operation to be set-up on site. 

Upon arrival at an office facility, we each went to our first assigned custodian office — and with empty archive boxes on hand, we’d start the review. We’d put numbered stickers on every file cabinet drawer and desk drawer to be reviewed. We’d label the outside of an archive box with the custodian’s name. Upon finding a responsive document, it was pulled out, an “out card” was put in its place in the original file (we wrote the number of pages of the document that was removed on the out card).  We created a file folder labeled with the number of the file cabinet/desk drawer, followed by the same title on the file from which the document was removed, and we placed the document in the folder, which went into the archive box.  An entire office was reviewed like this, and when we finished an office, we labeled each box with “1 of N”, “2 of N” and so on.

The next step was photocopying, which was quite an involved operation.  Most of this was ‘glass-work’ – that is, stacks of paper were not fed into the machine for bulk photocopying; rather, documents were photocopied one-by-one, by hand. This was necessary because staples, paper clips, and binder clips had to be removed, post-it notes had to be photocopied separately, spiral bound materials needed to be un-bound, and so on. A photocopy operator removed a document form an archive box, did the required preparation, made a photocopy, reassembled the original and put it back in the archive box, assembled the photocopy to match the original and placed it in a second archive box labeled the same as the first, and within the box, in a folder labeled the same as the original.  You get the picture. 

After photocopying, a second operator did a quality control review to ensure that everything copied properly and nothing was missed.  Originals were returned to the document reviewer to re-file, and the copies – which were now the ‘original working copy’ for purposes of litigation – were sent on to the next step… document numbering.  A sequential number was applied to every page using either a Bates stamp machine or a number label.  After numbering, documents were boxed for shipping.

After reviewing the office files, we usually moved on to a warehouse facility at which we used the same approach.  For the most part, the warehouse reviews were unpleasant.  Very often there was inadequate heat or air conditioning, poor ventilation, uncomfortable furniture, and lots of dust.  On the bright side, we got to wear jeans and t-shirts to work, which was unheard of in the days before ‘business casual’ and ‘casual Friday’ were the norm.

This operation was a pretty routine document collection project.  There was, however, one thing about this case that wasn’t routine at all.  After numbering, these documents were shipped to a litigation support service provider for document coding.  This was one of those rare, bet-your-company cases for which a database was built. In the next few blog posts in this series, I’ll describe the litigation support industry and a typical litigation support database.

Please let us know if there are eDiscovery topics you’d like to see us cover in eDiscoveryDaily.

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.