Campbell et al v. Facebook Inc.
Filing
72
STIPULATION WITH PROPOSED ORDER CORRECTION OF DOCKET # 70 filed by Matthew Campbell, Michael Hurley, David Shadpour. (Sobol, Michael) (Filed on 4/14/2015)
1
2
3
4
UNITED STATES DISTRICT COURT
5
NORTHERN DISTRICT OF CALIFORNIA
6
7
8
MATTHEW CAMPBELL, MICHAEL
HURLEY, and DAVID SHADPOUR, on
behalf of themselves and all others
similarly situated,
Plaintiffs,
9
10
STIPULATED [PROPOSED] ORDER
REGARDING ELECTRONIC
DISCOVERY
v.
11
Case No. C 13-05996 PJH (MEJ)
FACEBOOK, INC.,
Defendant.
12
13
14
15
1.
16
This Order will govern discovery of electronically stored information (“ESI”) in this case as a
PURPOSE
17
supplement to the Federal Rules of Civil Procedure, this Court’s Guidelines for the Discovery of
18
Electronically Stored Information, and any other applicable orders and rules. To the extent that any
19
issue addressed herein is also addressed in the parties’ Stipulated Protective Order (“Protective
20
Order”), the Protective Order shall govern.
21
2.
22
The parties are aware of the importance the Court places on cooperation and commit to
COOPERATION
23
cooperate in good faith throughout the matter consistent with this Court’s Guidelines for the
24
Discovery of ESI.
25
3.
26
The parties have discussed their preservation obligations and needs and agree that
27
PRESERVATION
preservation of potentially relevant ESI will be reasonable and proportionate.
28
1
Gibson, Dunn &
Crutcher LLP
STIPULATED ORDER RE: DISCOVERY OF ELECTRONICALLY STORED INFORMATION
CASE NO. 13-05996-PJH (MEJ)
1
2
This section is not intended to curtail or modify the parties’ rights or obligations under the
Federal Rules, including the obligation to preserve evidence.
3
4.
4
The parties agree that they will meet and confer to identify custodians whose ESI will be
SEARCH
5
searched for responsiveness to document requests, subject to the responding party’s objections to
6
document requests.
7
5.
8
ESI productions shall be de-NISTed using the industry standard list of such files maintained
9
DE-NISTING & FILE TYPE FILTERS
in the National Software Reference Library by the National Institute of Standards & Technology.
10
Upon request of a receiving party, a producing party shall identify any additional standard, readable,
11
and reviewable file types that have been excluded from its document production and that the
12
producing party has reason to believe may include relevant and responsive discoverable information,
13
for any production made following the date of this Order, and will utilize reasonable best efforts to do
14
the same with respect to any productions made prior to the date of this Order. Any party to whom
15
such disclosure is made will have ten business days to object. Any objection not made in this period
16
will be waived. If objections are made, the relevant parties will meet and confer to resolve them.
17
6.
18
The parties will produce all documents as single page black and white TIFF format files
PRODUCTION FORMATS
19
imaged at 300 dpi, Group IV compression; name each TIFF file with a unique name matching the
20
Bates number labeled on the corresponding page; do not create a separate folder for each document;
21
and use the time zone associated with the original document when processing documents that were
22
originally stored as native electronic files. The parties agree not to degrade the searchability of
23
documents as part of the document production process. The searchable, extracted text for redacted
24
documents will be replaced with OCR text.
25
26
ESI shall be processed, to the extent practicable, in a manner that preserves hidden columns or
rows, hidden text or worksheets, speaker notes, tracked changes and comments.
27
28
2
Gibson, Dunn &
Crutcher LLP
STIPULATED ORDER RE: DISCOVERY OF ELECTRONICALLY STORED INFORMATION
CASE NO. 13-05996-PJH (MEJ)
1
Image Load File
2
All productions will be provided with data load files (.dat) and image (.opt) load files in
3
standard Concordance format. The image load file must reference each TIFF file in the
4
corresponding production, and the total number of TIFF files referenced in the load file must match
5
the total number of image files in the production. The total number of documents referenced in a
6
production’s data load file should match the total number of designated document breaks in the
7
corresponding image load file for that production.
8
Document Text
9
For documents that were originally stored as native electronic files and that do not have
10
redactions, the extracted, full text from the body of each document will be produced in a separate .txt
11
file named for the beginning Bates number of the document. For documents that were originally
12
stored as native electronic files and which have redactions, OCR text will be produced from the
13
redacted image(s) associated with each document as a separate .txt file for each document named for
14
the Bates number of the document. The text of the document shall not be included in the .dat file, but
15
instead the .dat file shall include a link to the .txt file. Any redacted material should be clearly
16
labeled to show the redactions on the TIFF image.
17
Databases and Enterprise Systems
18
To avoid production of entire large databases and enterprise systems, a party may opt to
19
produce responsive information from databases and enterprise systems in an alternate form, such as
20
an Excel spreadsheet or similar report, where practicable. Reports produced for this purpose shall be
21
produced in native format, along with a TIFF image of a slip sheet identifying the Bates stamp of the
22
native file. If the Microsoft Excel application is insufficient to accurately present the information, the
23
parties will meet and confer to discuss the best method of producing the information referenced in the
24
report or table. The parties agree to meet and confer regarding the production of enterprise database-
25
application files (e.g., SQL and SAP) identified for production to determine the most reasonable form
26
of production based on the specific circumstances.
27
28
3
Gibson, Dunn &
Crutcher LLP
STIPULATED ORDER RE: DISCOVERY OF ELECTRONICALLY STORED INFORMATION
CASE NO. 13-05996-PJH (MEJ)
1
Microsoft Excel, Other Spreadsheet Files, and Other Structured Data
2
Files created by Microsoft Excel, other spreadsheet programs, or Access, as well as files
3
containing other structured data shall be produced in native format with a corresponding TIFF image
4
of a slip sheet identifying the Bates stamp of the native file. The parties will provide a relative file
5
path or link to the native Excel in the production load file. The produced file should be named with
6
the Bates number of the first page of the corresponding TIFF production of the document (e.g.,
7
“ABC00001.xls”). The original file name shall be maintained in a way such that a party will be able
8
to search for the original file name.
9
10
11
Hard-Copy Documents
Any documents that exist in hard copy must be scanned and produced in the required
production format.
12
Special File Types
13
The parties agree that presentation-application files (e.g., MS PowerPoint), spreadsheet-
14
application files (e.g., MS Excel), and multimedia audio/visual files such as voice and video
15
recordings (e.g., .wav, .mpeg, and .avi) shall be produced in native format. In addition to producing
16
the above file types in native format, the producing party shall produce a single-page TIFF slipsheet
17
indicating that a native item was produced. The corresponding load file shall include NativeFileLink
18
information for each native file that is produced. Further, the parties agree to meet and confer
19
regarding producing native file types other than MS PowerPoint, MS Excel, and multimedia
20
audio/visual file types, such as .wav, .mpeg and .avi. The produced file should be named with the
21
Bates number of the first page of the corresponding TIFF production of the document (e.g.,
22
“ABC00001.ppt”). The original file name shall be maintained in a way such that a party will be able
23
to search for the original file name.
24
Confidentiality Designation
25
Responsive documents in TIFF format will be stamped with the appropriate confidentiality
26
designations in accordance with the Protective Order in this matter. Each responsive document
27
produced in a different native format will have its confidentiality designation identified in the
28
filename of the native file as well as the slip-sheet for the native file.
4
Gibson, Dunn &
Crutcher LLP
STIPULATED ORDER RE: DISCOVERY OF ELECTRONICALLY STORED INFORMATION
CASE NO. 13-05996-PJH (MEJ)
1
Document Metadata
2
Parties shall produce extracted metadata for each document in the form of a .dat file along
3
with standard Concordance image load file, and include the following fields to the extent available,
4
except that if the field contains privileged information, that privileged information may be
5
redacted. Any redactions for privilege reasons shall be recorded on a privilege log subject to
6
Section 10 below:
7
FIELD NAME
FIELD DESCRIPTION
8
BegBates
First Bates number (production number) of an item
9
EndBates
Last Bates number (production number) of an item
**The EndBates field should be populated for single-page items.
11
AttachName
File name of the attachment
12
BegAttach
First Bates number of family group
EndAttach
Last Bates number of attachment range (i.e., Bates number of the last page of the last attachment)
PgCount
Number of pages in the item
Custodian
Name of person from whose files the item is produced
CustodianOther
Name of the Custodian(s), in addition to the person whose name is in the Custodian field above, from
whose files the item would have been produced if it had not been de-duplicated
10
13
14
15
16
17
18
SourceFilePath
19
20
1
The directory structure or path where the original file was stored on the party’s source computer
system. Any container name (such as ZIP or PST containers) is included in the path
HashValue
NativeFileLink
Hyperlink path for documents provided in native format only
**The linked file must be named per the BegBates value.
FileExtension
Indicates file extension of source native file
DateSent
(mm/dd/yyyy)
21
The MD5 or IntMsgID hash value of the item
Date email or calendar item was sent
22
23
24
25
26
27
28
1
This field may be excluded if the producing party determines it includes information protected by
any applicable privilege or immunity.
5
Gibson, Dunn &
Crutcher LLP
STIPULATED ORDER RE: DISCOVERY OF ELECTRONICALLY STORED INFORMATION
CASE NO. 13-05996-PJH (MEJ)
1
FIELD NAME
FIELD DESCRIPTION
Time email or calendar item was sent
3
TimeSent
(hh:mmAM/PM)
4
DateReceived
Date email or calendar item was received
TimeReceived
Time email or calendar item was received
To
The names and/or SMTP email addresses of all recipients that were included on the “To” line of the
email or calendar item
From
The name and/or SMTP email address of the sender of the email or calendar item
CC
The names and/or SMTP email addresses of all recipients that were included on the “CC” line of the
email or calendar item
BCC
The names and/or SMTP email addresses of all recipients that were included on the “BCC” line of the
email or calendar item
AttachCount
Number of attached documents to an email or grouped items
DateCreated
(mm/dd/yyyy)
Date the item was created
TimeCreated
(hh:mm AM/PM)
Time the item was created
LastModifiedBy
Person who last modified or saved the item, as populated in the metadata or document properties of
the native file
LastModDate
(mm/dd/yyyy)
Date the item was last modified
LastModTime
(hh:mm AM/PM)
Time the item was last modified
22
FileName
The filename of the source native file for an ESI item
23
Title
Any value populated in the Title field of the source file metadata or item properties
Subject
Any value populated in the Subject field of the source file metadata or document properties (e.g.,
subject line of email or calendar item)
Author
Creator of the document; any value populated in the Author field of the source file metadata or
document properties
TextPath
Full relative path to the current location of the document-level text file specified in this Order.
2
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
24
25
26
27
28
6
Gibson, Dunn &
Crutcher LLP
STIPULATED ORDER RE: DISCOVERY OF ELECTRONICALLY STORED INFORMATION
CASE NO. 13-05996-PJH (MEJ)
1
FIELD NAME
FIELD DESCRIPTION
Redacted
User-generated field that will indicate redactions. “X,” “Y,” “Yes,” “True,” are all acceptable
indicators that the document is redacted. Otherwise, blank.
Confidentiality
User-generated field that will indicate confidentiality. “X,” “Y,” “Yes,” “True,” or the type of
confidentiality designation under the parties’ Protective Order are all acceptable indicators that the
document is Confidential. Otherwise, blank.
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
Security
Both parties will make reasonable efforts to ensure that any productions made are free from
viruses and provided on encrypted media.
Production Media
Documents shall be produced on readily accessible electronic media or delivered by Secure
File Transfer Protocol.
7.
DE-DUPLICATION
Parties may de-duplicate globally (e.g., across custodians) utilizing a standard, industry
acceptable methodology.
The parties agree that an email that includes content on the “bcc” or other blind copy field
shall not be treated as duplicate of an email that does not include content in the “bcc” or other blind
copy field, even if all remaining content in the email is identical. The parties will produce a single
unique copy of a given e-mail message and its attachments, or standalone file, with references to each
Custodian in which a copy originally appeared as set forth in the metadata specifications above. In
the case of duplicates maintained by Custodians in different time zones, it is understood that the
image and date/time metadata will reflect the time locally kept by each Custodian.
8.
PRODUCTION TIMING
The parties recognize that the production of ESI may take substantially more than 30 days to
process. The parties agree that rolling productions may be appropriate.
The parties reserve the right to request changes to the production protocol based on a
reasonable belief that such changes will decrease the burden of production without materially
changing the information produced.
28
7
Gibson, Dunn &
Crutcher LLP
STIPULATED ORDER RE: DISCOVERY OF ELECTRONICALLY STORED INFORMATION
CASE NO. 13-05996-PJH (MEJ)
1
9.
2
Each party agrees to retain native electronic source documents for all electronically stored
RETENTION OF ORIGINAL DOCUMENTS
3
information produced in this litigation. Each party agrees to use reasonable measures to maintain the
4
original native source documents in a manner so as to preserve the metadata associated with these
5
electronic materials as it existed at the time of the original production in the event the review of such
6
metadata becomes necessary. Notwithstanding this, each party understands and acknowledges that
7
producing the metadata may affect some changes in the metadata itself, and agrees that any metadata
8
change that results from production to requesting parties is permissible. The parties also understand
9
and acknowledge that metadata of some documents may have been modified during the normal
10
course of business or during investigation of the subject matter of this case and agree that any such
11
changes to metadata will not be considered spoliation of evidence.
12
10.
13
Inadvertent production and privilege log issues are governed by the parties’ Protective Order.
14
11.
15
Nothing in this Agreement shall be interpreted to require disclosure of irrelevant information
DOCUMENTS PROTECTED FROM DISCOVERY
SCOPE OF AGREEMENT
16
or relevant information protected by the attorney-client privilege, work-product doctrine, or any other
17
applicable privilege or immunity. The parties do not waive any objections as to the production,
18
discoverability, admissibility, or confidentiality of documents and ESI. This Order is intended to
19
govern the format of the parties’ production. Nothing in this Order affects the parties’ discovery
20
obligations under the Federal or Local Rules.
21
The parties reserve the right to request changes to the production protocol based on a
22
reasonable belief that such changes will decrease the burden of production without materially
23
changing the information produced.
24
12.
25
This Stipulated Order may be modified by a Stipulated Order of the parties or by the Court for
26
27
MODIFICATION
good cause shown.
IT IS SO STIPULATED, THROUGH COUNSEL OF RECORD.
28
8
Gibson, Dunn &
Crutcher LLP
STIPULATED ORDER RE: DISCOVERY OF ELECTRONICALLY STORED INFORMATION
CASE NO. 13-05996-PJH (MEJ)
1
Dated: April 14, 2015
2
3
4
LIEFF CABRASER HEIMANN & BERNSTEIN
LLP
By: /s/ Michael W. Sobol
Michael W. Sobol
Attorneys for Plaintiffs
5
6
GIBSON, DUNN & CRUTCHER, LLP
7
By: /s/ Joshua A. Jessen
Joshua A. Jessen
Attorneys for Defendant Facebook, Inc.
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
9
Gibson, Dunn &
Crutcher LLP
STIPULATED ORDER RE: DISCOVERY OF ELECTRONICALLY STORED INFORMATION
CASE NO. 13-05996-PJH (MEJ)
1
2
3
ATTESTATION
I, Michael W. Sobol, am the ECF user whose identification and password are being used to
file this Stipulation. I hereby attest that Joshua A. Jessen has concurred in this filing.
4
/s/ Michael W. Sobol
Michael W. Sobol
5
6
7
8
9
PURSUANT TO STIPULATION, IT IS SO ORDERED.
DATED: ______________________
_____________________________________
The Honorable Phyllis J. Hamilton
United States District Judge
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
10
Gibson, Dunn &
Crutcher LLP
STIPULATED ORDER RE: DISCOVERY OF ELECTRONICALLY STORED INFORMATION
CASE NO. 13-05996-PJH (MEJ)
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?