Christine Taylor

Network Computing Blogger


Upcoming Events

Interop NY
Oct. 1-5

Interop is the only event to give you a comprehensive and unbiased understanding of all the latest innovations-including cloud computing, virtualization, security, mobility and data center advances-that help position your company for growth.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

Tags: , , , ,

Channel: Data Protection, E-discovery

See more from this blogger

When It Comes to eDiscovery, Even Walmart Can Get It Wrong

Mimosa Systems' excellent (and entertaining) Know-It-All Guide recently reminded me of an older but still relevant case, Testa vs. Walmart. The mid-90s case is still relevant because the same practices that led to Walmart's loss happen every day in business. The settlement was small at $50K and Walmart could readily afford it, but do you really want to go there by making the same mistake they did?

Here is a short summary. In 1993 Louis R. Testa drove up to a Walmart loading dock. The dock was coated with ice but Testa gamely delivered his load of tropical fish with a dock worker's help. Sadly he slipped and fell on the ice and threatened to sue right then and there. The Walmart employee alerted his supervisors who ordered a full investigation. The finished report included photos of the ramp, a description of events and Testa's threat to sue.

Three years later, he did sue. Walmart's defense? That an invoice clerk had contacted all of the store's vendors just the day before to tell them that Walmart would not be receiving any deliveries on that day. This is why the loading ramp was icy: the store expected no deliveries and so had not cleared it. And they might have made their case - except that 2 years after the incident, the clerk's contact records were deleted as part of a corporate-wide deletion policy. The incident report survived.

Walmart ended up losing the case both in district court and on appeal. Although the invoice clerk testified to her actions, Walmart could not produce the records that might have exonerated them. The retailer had recorded Testa's threat to sue and should have preserved the clerk's contact records. Even proving a corporate deletion policy did not excuse them from destroying records that were relevant to a reasonable expectation of litigation.

Don't get me wrong -- a deletion policy is a good thing in general, since corporations commonly keep much more data than they should. Automated data retention and retirement goes a long way towards keeping storage costs lean and mean, and speeds up data searches by controlling the size of ESI. But it is not as simple as that. When records are related to a possible lawsuit - especially one that was quite likely to happen - there must be policies in place to preserve them until settlement, or until a statute of limitations has passed. Archival management with deep eDiscovery options is a must in these cases, and I urge you to look at companies like Mimosa to do it.

Related Reading


More Insights




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Research and Reports

Storage Virtualization Guide
May 2012

Network Computing: May 2012

TechWeb Careers