MICHELLE L. PETERSON, Magistrate Judge.
The parties hereby stipulate to the following provisions regarding the discovery of electronically stored information ("ESI") in this matter:
1. An attorney's zealous representation of a client is not compromised by conducting discovery in a cooperative manner. The failure of counsel or the parties to litigation to cooperate in facilitating and reasonably limiting discovery requests and responses raises litigation costs and contributes to the risk of sanctions.
2. The proportionality standard set forth in Fed. R. Civ. P. 26(b)(1) must be applied in each case when formulating a discovery plan. To further the application of the proportionality standard in discovery, requests for production of ESI and related responses should be reasonably targeted, clear, and as specific as possible.
Within 20 days after the date the parties sign this Agreement, each party shall disclose:
1.
2.
3.
4.
The parties acknowledge that they have a common law obligation to take reasonable and proportional steps to preserve discoverable information in the party's possession, custody or control. With respect to preservation of ESI, the parties agree as follows:
1. Absent a showing of good cause by the requesting party, the parties shall not be required to modify the procedures used by them in the ordinary course of business to back-up and archive data; provided, however, that the parties shall preserve all discoverable ESI in their possession, custody or control.
2. All parties shall supplement their disclosures in accordance with Rule 26(e) with discoverable ESI responsive to a particular discovery request or mandatory disclosure where that data is created after a disclosure or response is made (unless excluded under (C)(3) or (D)(1)-(2) below).
3. Absent a showing of good cause by the requesting party, the following categories of ESI need not be preserved:
1. With respect to privileged or work-product information generated after the filing of the complaint, parties are not required to include any such information in privilege logs.
2. Activities undertaken in compliance with the duty to preserve information are protected from disclosure and discovery under Fed. R. Civ. P. 26(b)(3)(A) and (B).
3. Information produced in discovery that is protected as privileged or work product shall be immediately returned to the producing party, and its production shall not constitute a waiver of such protection, if: (i) such information appears on its face to have been inadvertently produced or (ii) the producing party provides notice within 30 days of discovery by the producing party of the inadvertent production.
4. Privilege Log Based on Metadata. The parties agree that privilege logs shall include a unique identification number for each document and the basis for the claim (attorney-client privileged or work-product protection). For ESI, the privilege log may be generated using available metadata, including author/recipient or to/from/cc/bcc names; the subject matter or title and date created. Should the available metadata provide insufficient information for the purpose of evaluating the privilege claim asserted, the producing party shall include such additional information as required by the Federal Rules of Civil Procedure.
1.
2.
a. A producing party shall disclose the search terms or queries, if any, and methodology that it proposes to use to locate ESI likely to contain discoverable information. The parties shall meet and confer to attempt to reach an agreement on the producing party's search terms and/or other methodology.
b. If search terms or queries are used to locate ESI likely to contain discoverable information, a requesting party is entitled to no more than 5 additional terms or queries to be used in connection with further electronic searches absent a showing of good cause or agreement of the parties. The 5 additional terms or queries, if any, must be provided by the requesting party within 14 days of receipt of the producing party's production.
c. Focused terms and queries should be employed; broad terms or queries, such as product and company names, generally should be avoided. Absent a showing of good cause, each search term or query returning more than 250 megabytes of data is presumed to be overbroad, excluding Microsoft PowerPoint files, image and audio files, and similarly large file types.
d. The producing party shall search both non-custodial data sources and ESI maintained by the custodians identified above.
3.
a. Responsive Documents shall be produced in image format, with load files that are compatible with Concordance and Ipro (.OPT / .DAT). The images shall be produced in black & white, single-page, 300 DPI, Group IV .tiff images. Extracted text shall be provided for each Document as document level text files and a path to the document level text file shall be included in the load file. All images should be branded with the Bates number assigned to each page, in the lower right hand corner in such a fashion as to not obscure any portion of the image. Original Document orientation should be maintained to the extent possible.
b. Each Document load file shall include the following fields (to the extent such fields are available) of searchable metadata or information:
In the case of e-mail, text message, or other written communication, whether transmitted or drafted, the load files shall also include (to the extent such fields are available):
c. In the case of other non-e-mail electronic files (e.g., Microsoft Word, Microsoft Excel, etc.), the load files shall also include (to the extent such fields are available):
d. All Documents whose native format is that of a Microsoft Excel file (or other electronic spreadsheet file) or other Documents where .tiff images do not adequately communicate the substantive content or context of the file (e.g., multimedia files, databases) shall be produced with a single-page placeholder (Group IV .tiff image) indicating that the file has been produced natively and shall be produced in its original native format, including, but not limited to the logical formulae within the cells of any spreadsheet and any metadata contained in the file. In the case of any databases and/or files created in proprietary applications, the parties should discuss whether a standard export of structured data into a commonly used application (e.g., Microsoft Access or SQL) would be appropriate or whether there is some other form of production or reporting that would be more appropriate.
e. For Documents that have been redacted, Optical Character Recognition ("OCR") matching the redacted version of the Document shall be provided as "text" for such documents. To the extent any Document that would have been produced in native format pursuant to the instruction above has been redacted, .tiff images and OCR of the redacted document will suffice in lieu of a native file. The parties will, however, make reasonable efforts to ensure that any such Documents that are produced only as .tiff images are formatted so as to be readable.
f. Notwithstanding the foregoing, if any Documents are produced in a form that is not reasonably useable by the undersigned, the undersigned reserves the right to request specific and individual records to be delivered in a different form, including, but not limited to, native format. Further, the right to demand production of any other responsive Documents in their native format (including all metadata) is expressly reserved, and the parties shall preserve all Documents to which a duty of preservation attaches in their native format (including all metadata).
g. Parties may produce documents via a secure file transfer mechanism or on readily accessible computer or electronic media as the Parties may hereafter agree upon, including secure password-protected electronic download (e.g., SFTP)or external hard drive. All production media will be encrypted and the producing party will provide a decryption key to the requesting party in a communication separate from the production itself.
4.
IT IS SO STIPULATED, THROUGH COUNSEL OF RECORD
Based on the foregoing, IT IS SO ORDERED.