AIIM Infonomics just published my contributed article titled “Data Mapping Nuts and Bolts” in their April 13, 2010 issue. While there are many articles and white papers on data mapping, when I was asked to write this article, I took a look at the existing material and realized that I had not run across a concise list of reasons to perform data mapping. So for this article, I provided just that along with a definition of data mapping to meet those requirements. The full AIIM article provides in-depth information covering both my definition of data mapping, the requirements it addresses, as well as implementation steps, and integration with a full end-to-end eDiscovery solution.
A data map is a listing of the organization’s ESI by category, location, and custodian or steward, including how it is stored, its accessibility, and associated retention policies and procedures.
- Data map for delivery to opposing party: FRCP Rule 26(a)(1)(A)
- Meet & confer meeting preparation: FRCP Rule 26(f)
- Not reasonably accessible argument support: FRCP Rule 26(b)(2)
- Safe harbor and sanction avoidance: Rule 37(e)
For more information, read the full article on AIIM.org.