GSI Technology, Inc. v. Cypress Semiconductor Corporation

Filing 42

ORDER GRANTING 39 STIPULATION Regarding Production Format of Electronically Stored Information. Signed by Judge Edward J. Davila on 9/13/2012. (ejdlc1, COURT STAFF) (Filed on 9/13/2012)

Download PDF
1 2 3 4 5 6 7 Lee H. Rubin (CBA 141331) lrubin@mayerbrown.com Christopher J. Kelly (CBA 276312) cjkelly@mayerbrown.com MAYER BROWN LLP Two Palo Alto Square, Suite 300 3000 El Camino Real Palo Alto, CA 94306-2112 Telephone: (650) 331-2000 Facsimile: (650) 331-2060 Attorneys for Defendant Cypress Semiconductor Corporation 8 9 UNITED STATES DISTRICT COURT 10 NORTHERN DISTRICT OF CALIFORNIA 11 SAN JOSE DIVISION 12 GSI Technology, Inc., Plaintiff, 13 v. 14 15 Case No. 5:11-cv-03613 EJD Cypress Semiconductor Corporation, STIPULATION REGARDING PRODUCTION FORMAT OF ELECTRONICALLY STORED INFORMATION Defendant. 16 17 18 19 1. General Specifications (a) This Stipulation represents the agreement among the parties on technical 20 specifications regarding production of Electronically Stored Information (“ESI”). 21 The parties reserve for future discussion substantive issues that might arise related 22 to the production of ESI. This Stipulation does not concern production of 23 transactional database information. 24 (b) Documents will be produced as TIFF files (with extracted text or OCR and 25 metadata when available), unless otherwise specified below. Aside from the 26 document categories below, the parties will meet and confer to discuss any 27 requests for the production of documents in native format on a case-by-case basis 28 where good cause exists for such request. STIPULATION REGARDING PRODUCTION FORMAT OF ELECTRONICALLY STORED INFORMATION CASE NO. 5:11-CV-03613 EJD 702928428 1 (c) Metadata will include fields described below. 2 (d) Image cross reference files will function with Opticon viewer. 3 (e) Media volume names will have the producing party’s internal tracking ID. 4 (f) A party may produce a single copy of a responsive document and a party may de- 5 duplicate responsive ESI (for example, based on MD5 or SHA-1 hash values at 6 the document level) across custodians, insofar as absolutely no non-duplicative 7 information is lost as a result. For emails with attachments, the hash value is 8 generated based on the parent/child document grouping. A party may also de- 9 duplicate “near-duplicate” email threads as follows: in an email thread, only the 10 final-in-time document need be produced, if and only if all previous emails (and 11 all other information, such as authors, recipients, time sent and received, etc.) in 12 the thread are contained within the final message. In addition, only a single copy 13 of an email need be produced even where it was sent to multiple recipients, if and 14 only if all information contained in other copies (such as time sent and received, 15 authors, recipients, etc.) is contained within the single copy. Where a prior email 16 contains an attachment, that email and attachment shall not be removed as a 17 “near-duplicate.” (g) 18 Hardcopy Documents – The parties may produce, at the producing party’s option, 19 hardcopy documents in hard copy or TIFF format. If a document that was 20 originally generated by a software application (e.g., Microsoft Word or Microsoft 21 Outlook) is collected from a custodian in hard copy form, the producing party has 22 no obligation to locate and produce the electronic file from which the hard copy 23 was created. However, if the electronic file would otherwise be gathered as part 24 of the producing party’s collection, both the electronic file and the hard copy shall 25 be produced. 26 27 2. Output Files (a) 28 Extracted Text: Control List (.lst or equivalent) -2STIPULATION REGARDING PRODUCTION FORMAT OF ELECTRONICALLY STORED INFORMATION CASE NO. 5:11-CV-03613 EJD 702928428 1 (b) Image Index Files: Opticon (.opt) 2 (c) Metadata Files: Concordance (.dat) 3 3. Output Folder Structure (a) 4 production. 5 (b) 6 7 8 9 10 11 12 The producing party will manually create the top level directory prior to TIFF and text files for a single document will always be in the same folder. Directory Structure ___<VFID-Media#>.dat,<VFID-Media#>.lfp ___<VFID-Media#> | |___Folder# (01) | |__BatesNumber.tif | |__BatesNumber.tif | |__BatesNumber.tif | |___Folder# (02) | |__BatesNumber.tif | |__BatesNumber.tif | |__BatesNumber.tif Standard with Padding ___XXX01-01.dat, XXX01-01.lfp ___XXX01-01 | |___01 | |__EXAMPLE00000001.tif | |__EXAMPLE00000001.txt | |__EXAMPLE00000002.tif | |___02 | |__EXAMPLE00000501.tif | |__EXAMPLE00000501.txt | |__EXAMPLE00000502.tif 13 14 4. General Configuration 15 (a) Documents will not be broken across multiple Media folders. 16 (b) Produce TIFF files in single page format at 300 DPI. 17 5. Text Files (.txt) 18 (a) Produce text files or OCR on a per-document basis. 19 (b) Name text files according to the corresponding first page (BegDoc#) of the document. 20 (c) 21 22 23 6. Do not truncate. Native Files (a) Absent a showing that a particular file, or category of files, is not reasonably 24 accessible, the parties will produce Microsoft Excel files, Microsoft PowerPoint 25 files, and media files in native format with a link in the NativeLink field, along 26 with extracted text or OCR and applicable metadata fields set forth in Section 8. 27 28 -3STIPULATION REGARDING PRODUCTION FORMAT OF ELECTRONICALLY STORED INFORMATION CASE NO. 5:11-CV-03613 EJD 702928428 1 A TIFF placeholder indicating the document was produced in native format shall 2 accompany the database record. (b) 3 Non-Microsoft files that are the functional equivalents to Microsoft Excel and 4 Microsoft PowerPoint files (such as Apple Numbers and Apple Keynote files) 5 shall be produced in TIFF format in the first instance, with extracted text or OCR 6 and applicable metadata. Native format versions of these files shall be produced 7 upon individual identification and request if available. (c) 8 To the extent Microsoft Excel files, Microsoft PowerPoint files, or their functional equivalents require redaction, the producing party will produce TIFF 9 10 images with OCR and metadata when available, in lieu of a native file and 11 extracted text. (d) 12 To the extent a document is produced both in native format and as a TIFF, the 13 parties will use the TIFF version as an exhibit in depositions, briefs, hearings, or 14 at trial. The parties will meet and confer to discuss any requests for the use of 15 documents in native format on a case-by-case basis. 16 7. Family Range Configuration (a) 17 Part 8. 18 19 Family structure will be maintained in productions and identified by the fields in 8. Use Concordance Metadata Load Files (.dat) 20 (a) Load files will contain one line per document. 21 (b) Load files will have the field names as the as first row of data. 22 (c) Concordance metadata load files will include the following: 23 24 25 26 Field Name BegBates (BegDoc#) EndBates (EndDoc#) BegAttach 27 28 Description StartBates Production number Endbates Production number Beginning unique identification number for any attachment or range of attachments -4- (Comments) Include prefix and padding Include prefix and padding Field Type Limited Text Limited Text Limited Text STIPULATION REGARDING PRODUCTION FORMAT OF ELECTRONICALLY STORED INFORMATION CASE NO. 5:11-CV-03613 EJD 702928428 1 2 Field Name EndAttach 3 4 Source 5 MediaSource (DocumentType) DateSent 6 7 8 DateCreated 9 10 FileName 11 FileSize 12 13 Doc Ext (Extension) 14 Subject 15 From 16 To Description (Comments) Ending unique Include prefix and identification padding number for any attachment or range of attachments Custodian or Source of document File Type Email, File, etc Field Type Limited Text Date Email was Sent (MMDDYYYY) Date (MMDDYYYY) Created, if any, as found in native file when collected File name of the file Applies to emails Date Will be blank for email Date Will be blank for email Full Text File size (as megabytes) The document extension of the document Subject line of Email Sender Recipient [Delimited list] Cc Bcc 23 Author 24 DocTitle Filename 25 Confidentiality 26 ORIGINALPATH 27 28 Will be blank if 0 Limited Text Will be blank for Files Will be blank for Files Include multivalue Full Text Full Text Full Text Full Text Bcc [Delimited list] Will be blank for Files Include multivalue Full Text Will be blank for Files Will be blank for email 21 22 Limited Text Cc [Delimited list] 19 20 Limited Text Will be blank for Files Include multivalue 17 18 Full Text Information contained in the author field, if any Information contained in the title field, if any Confidentiality Include multivalue designation of the document Data’s source path Will be blank for information, unless email path name contains Full Text Full Text Full Text Full Text -5STIPULATION REGARDING PRODUCTION FORMAT OF ELECTRONICALLY STORED INFORMATION CASE NO. 5:11-CV-03613 EJD 702928428 1 Field Name Description privileged information; where file was stored on custodian’s hard drive or network resource Email folder path (sample: Inbox\active) [Blank for files] Indicates if document contains redaction Native File Link for MS Excel and MS PowerPoint documents produced in native format 2 3 4 5 [included in ORIGINALPATH] 6 7 8 Redacted NATIVE LINK 9 10 11 12 9. 16 17 18 19 20 Full Text Include multivalue Full Text If field encapsulators or separators are found in the metadata they will be replaced with another character or space. 14 15 Field Type Metadata Load File Delimiters (a) 13 (Comments) Type Field Encapsulate Field Separator Multi-value Delimiter New Line Indicator Dates are stored Character/Format Ctrl Character "þ" (Decimal 254) Ctrl Character "□"(Decimal 020) Semi Colon "; " (Decimal 59 space) Registered Symbol "®" (Decimal 174) Replace with Space " "(Decimal 032) Space " "(Decimal 032) N/A MMDDYYYY N/A N/A Notes Text line separator, used in TextInfo only. 21 22 10. OCR Index Files (.lst or equivalent) 23 (a) Follow the example above for format and delimiters. 24 (b) Bold is constant, Italics are variable, and pay attention to the use of commas and semicolons. 25 26 (c) Each file will contain one line per TIFF. 27 (d) Format: BatesPage,\TextPath\TextFileName.txt 28 -6STIPULATION REGARDING PRODUCTION FORMAT OF ELECTRONICALLY STORED INFORMATION CASE NO. 5:11-CV-03613 EJD 702928428 1 (e) Example: ABC00100000,\02501-01\01\ABC00100000.txt 2 (f) Definition of Components: 3 BatesPage Folder# 4 5 6 BatesPage value from metadata file. The number of the folder containing the TIFF. Text files will be named with a bates number.txt (Bates Padding/Prefix Configuration Section). Determine New Document Indicator Values. Y – if the TIFF is the first page of any document. BLANK – for all other pages. Number of pages in the document. TextFileName NewDocIndicator 7 8 9 10 11 PageCount 11. Opticon Image Index File (a) (i) 12 13 16 17 18 19 20 21 22 23 24 (ii) Example: xxx00100000,VolName002,yyy01-1\1\xxx00100000.tif,Y,,,4 (iii) BatesPage VolumeName TIFFPath VFID# Media# Folder# TIFFFileName NewDocIndicator 25 26 27 Format: BatesPage,VolumeName,TIFFPath\TIFFFileName.tif,NewDocIndicator,,,PageCount 14 15 Follow the example above for format and delimiters. PageCount 28 Definition of Components: BatesPage value from metadata file. The volume name of the Media containing the TIFFs. VFID#-Media#\Folder# The number of the Virtual Folder that the TIFF originated from The number of the Media containing the TIFF The number of the folder containing the TIFF TIFFs will be named with a bates number.tif (Bates Padding/Prefix Configuration Section) Determine New Document Indicator Values Y – if the TIFF is the first page of any document. BLANK – for all other pages. Number of pages in the document -7STIPULATION REGARDING PRODUCTION FORMAT OF ELECTRONICALLY STORED INFORMATION CASE NO. 5:11-CV-03613 EJD 702928428 1 2 3 4 5 Pursuant to Civil L.R. 5-1(i)(3), counsel for Defendant attests that Robert E. Schaberg, counsel for Plaintiff, has concurred in this filing. IT IS SO STIPULATED, THROUGH COUNSEL OF RECORD. DATED: August 31, 2012 /s/ Robert E. Schaberg Robert E. Schaberg Shartsis Friese LLP Attorneys for Plaintiff GSI Technology, Inc. DATED: August 31, 2012 /s/Lee H. Rubin Lee H. Rubin Mayer Brown LLP Attorneys for Defendant Cypress Semiconductor Corporation 6 7 8 9 10 11 12 13 PURSUANT TO STIPULATION, IT IS SO ORDERED. DATED: 14 September 12 _______________, 2012 Edward J. Davila United States District Court Judge 15 16 17 18 19 20 21 22 23 24 25 26 27 28 -8STIPULATION REGARDING PRODUCTION FORMAT OF ELECTRONICALLY STORED INFORMATION CASE NO. 5:11-CV-03613 EJD 702928428

Disclaimer: Justia Dockets & Filings provides public litigation records from the federal appellate and district courts. These filings and docket sheets should not be considered findings of fact or liability, nor do they necessarily reflect the view of Justia.


Why Is My Information Online?