Discovery requests are increasingly targeting email archives, content management systems and other semi-structured data sources. Most of these sources include search and retrieval features, so one could assume that this makes them a safer candidate for in-house collections. This is not automatically true and it’s definitely worth talking through some of the common problems that can lead to incomplete or altered retrievals. The first thing to realize is that these systems were not designed to comply with legal discovery requests as found in the United States. The search and retrieval functionality was added to support a business user seeking to find a few specific emails or an IT administrator restoring a larger set of items that were either lost or need to be transferred to a new user. Both of these scenarios stress quick, simple search without needing to verify the accuracy or integrity of the search or restoration.
Does this mean that these systems cannot be used to comply with discovery requests? They should not be used for legal requests without a thorough understanding of their architecture, component technologies, and the overall data lifecycle. This gives you the foundation to answer hard questions about how your communications and files have flowed into the system, what happens to them, who had access, how they could have been changed and how they are reassembled when they are retrieved.
via Discovery on Enterprise Archives and Content Platforms | eDiscovery Journal.



