At a recent discovery conference, opposing counsel asked why I wanted ESI produced in native and near-native formats. Her question struck me as curious. She intended to work with native formats to perform her own review. But when it came time to produce the gigabytes of e-mail, productivity documents, spreadsheets, and database exports, she meant to convert everything to .tiff images. “Where electronically stored information is concerned,” I thought, “lawyers make the Amish look wired.”
Still, “why native?” was a fair question. Assuming she’d commit to capture certain metadata fields, expose tracked changes before imaging, and produce load files with extracted text, we could make .tiff images work for everything but spreadsheets and databases.
This content has been archived. It is available through our partners, LexisNexis® and Bloomberg Law.
To view this content, please continue to their sites.
Not a Lexis Subscriber?
Subscribe Now
Not a Bloomberg Law Subscriber?
Subscribe Now
LexisNexis® and Bloomberg Law are third party online distributors of the broad collection of current and archived versions of ALM's legal news publications. LexisNexis® and Bloomberg Law customers are able to access and use ALM's content, including content from the National Law Journal, The American Lawyer, Legaltech News, The New York Law Journal, and Corporate Counsel, as well as other sources of legal information.
For questions call 1-877-256-2472 or contact us at [email protected]
