Colucci et al v. ZonePerfect Nutrition Company
Filing
53
Order by Hon. Samuel Conti granting 51 Stipulation Concerning the Protocol for Production of Documents.(sclc2, COURT STAFF) (Filed on 2/20/2013)
1
2
3
4
Janet Lindner Spielberg (SBN 221926)
LAW OFFICES OF JANET
LINDNER SPIELBERG
12400 Wilshire Boulevard, #400
Los Angeles, CA 90025
Tel: (310) 392-8801
Fax: (310) 278-5938
jlspielberg@jlslp.com
Elizabeth L. Deeley (SBN 230798)
KIRKLAND & ELLIS LLP
555 California Street
San Francisco, CA 94104
Tel: (415) 439-1400
Fax: (415) 439-1500
elizabeth.deeley@kirkland.com
5
6
7
8
Gregg F. LoCascio, P.C. (admitted pro hac vice)
Jonathan D. Brightbill (admitted pro hac vice)
Dennis J. Abdelnour (admitted pro hac vice)
KIRKLAND & ELLIS LLP
655 Fifteenth Street, NW
Washington, DC 20005
Tel: (202) 879-5000
Fax: (202) 879-5200
gregg.locascio@kirkland.com
jonathan.brightbill@kirkland.com
dennis.abdelnour@kirkland.com
Michael D. Braun (SBN 167416)
BRAUN LAW GROUP, P.C.
10680 West Pico Boulevard, Suite 280
Los Angeles, CA 90064
Tel: (310) 836-6000
Fax: (310) 836-6010
service@braunlawgroup.com
9
10
11
12
13
14
15
Joseph N. Kravec Jr. (admitted pro hac vice)
Maureen Davison-Welling (pro hac to be filed)
Wyatt A. Lison (pro hac to be filed)
STEMBER FEINSTEIN DOYLE
PAYNE & KRAVEC LLC
Allegheny Building, 17th Floor
429 Forbes Avenue
Pittsburgh, PA 15219
Tel: (412) 281-8400
Fax: (412) 281-1007
jkravec@stemberfeinstein.com
mdavidsonwelling@stemberfeinstein.com
wlison@stemberfeinstein.com
Attorneys for Defendant
ZONEPERFECT NUTRITION COMPANY
16
17
Attorneys for Plaintiff
KIMBERLY S. SETHAVANISH
18
UNITED STATES DISTRICT COURT
19
NORTHERN DISTRICT OF CALIFORNIA
20
21
SAN FRANCISCO DIVISION
KIMBERLY S. SETHAVANISH,
22
23
24
25
)
)
)
)
)
)
)
)
)
)
)
Plaintiff,
vs.
ZONEPERFECT NUTRITION COMPANY,
Defendant.
26
CASE NO. 12-CV-02907 SC
STIPULATION AND [PROPOSED]
ORDER CONCERNING THE
PROTOCOL FOR PRODUCTION OF
DOCUMENTS
27
28
1
STIPULATION CONCERNING THE PROTOCOL
FOR PRODUCTION OF DOCUMENTS
CASE NO. 12-CV-02907-SC
1
1.
PURPOSE
2
This Order will govern discovery of electronically stored information (“ESI”) in this case as
3
a supplement to the Federal Rules of Civil Procedure, this Court’s Guidelines for the Discovery of
4
Electronically Stored Information, and any other applicable orders and rules.
5
2.
COOPERATION
6
The parties are aware of the importance the Court places on cooperation and commit to
7
cooperate in good faith throughout the matter consistent with this Court’s Guidelines for the
8
Discovery of ESI.
9
3.
LIAISON
10
The parties have identified liaisons to each other who are and will be knowledgeable about
11
and responsible for discussing their respective ESI. Each e-discovery liaison will be, or have access
12
to those who are, knowledgeable about the technical aspects of e-discovery, including the location,
13
nature, accessibility, format, collection, search methodologies, and production of ESI in this matter.
14
The parties will rely on the liaisons, as needed, to confer about ESI and to help resolve disputes
15
without court intervention.
16
4.
PRESERVATION
17
The parties have discussed their preservation obligations and needs and agree that
18
preservation of potentially relevant ESI will be reasonable and proportionate. To reduce the costs
19
and burdens of preservation and to ensure proper ESI is preserved, the parties agree that:
20
21
22
23
24
25
(a) Only ESI in the form of e-mail, Network Shares/Homes Shares, and other custodianbased ESI created or received before June 30, 2012 will be preserved; otherwise, only
ESI created or received before June 30, 2013 will be preserved.
(b) The parties have exchanged a list of the types of ESI they believe should be preserved
and descriptions of the custodians for whom they believe ESI should be preserved. The
parties shall add or remove custodians as reasonably necessary.
(c) Among the sources of data the parties agree are not reasonably accessible, the parties
agree not to preserve the following: digital voicemail, instant messaging, backup media,
back-up tapes of Network Shares/Home Shares, back-up tapes of email, and disaster
recovery tapes.
26
27
(d) In addition to the agreements above, the parties agree data from these sources (a) could
contain relevant information but (b) under the proportionality factors, should not be
preserved: automatically saved versions of documents.
28
2
STIPULATION CONCERNING THE PROTOCOL
FOR PRODUCTION OF DOCUMENTS
CASE NO. 12-CV-02907-SC
1
5.
SEARCH
2
The parties agree that in responding to an initial Fed. R. Civ. P. 34 request, or earlier if
3
appropriate, they will meet and confer about methods to search ESI in order to identify ESI that is
4
subject to production in discovery and filter out ESI that is not subject to discovery.
5
6.
6
7
8
9
DE-DUPLICATION
To the extent that exact duplicate documents (based on MD5 or SHA-1 hash values) reside
within a party’s ESI data set, each party may produce only a single copy of a responsive document
or record (“Single Production Copy”). Exact duplicates will be identified through calculation of
MD5 or SHA-1 hash value and all de-duplication will occur at a family level.
10
7.
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
PRODUCTION FORMATS
A.
Form of Production. The parties will produce all documents as Group IV single
page black and white TIFF format files imaged at 300 dpi, except that product labels and print
advertisements which exist in color shall be produced in color. For all other documents (which will
be produced in black and white) the producing party will honor reasonable requests made in good
faith for either the production of the original document for inspection and copying or production of a
color image of the document. Name each TIFF file with a unique name matching the Bates number
labeled on the corresponding page. Image volumes will be limited to 1000 TIFF files.
1.
When processing ESI for review and for production in TIFF format, the
producing party will instruct its vendor to force off Auto Date and unhide al hidden objects.
2.
When processing ESI, EST should be selected as the time zone and the
producing party will note the time zone used in its processing. To the extent that a party has already
processed ESI using a different time zone, the producing party will note the time zone used in its
processing. Otherwise, Parties shall consistently produce all ESI processed using the same time
zone. When a metadata field includes a date, the date shall be provided in the format defined in
Section 7.K. below.
3.
The parties shall meet and confer to the extent reasonably necessary to
facilitate the import and use of the produced materials with commercially available document
28
3
STIPULATION CONCERNING THE PROTOCOL
FOR PRODUCTION OF DOCUMENTS
CASE NO. 12-CV-02907-SC
1
management or litigation support software.
2
3
B.
Image Load File. Provide an image load file (e.g., Opticon file or LFP) that contains
document boundaries.
4
C.
Document Text. For documents containing extractable text that were originally
5
stored as native electronic files and which do not have redactions, the extracted, full text from the
6
body of each document will be produced in a separate .txt file named for the beginning Bates
7
number of the document. For documents that were originally stored as native electronic files and
8
which have redactions, OCR text will be produced from the redacted image(s) associated with each
9
document as a separate .txt file for each document named for the Bates number of the document.
10
Any redacted, privileged material should be clearly labeled to show the redactions on the TIFF
11
image.
12
D.
Excel and Other Spreadsheet Files. Files created by Microsoft Excel or other
13
spreadsheet programs shall be produced in native format with corresponding TIFF images of Bates-
14
stamped slip sheets and appropriate confidentiality labeling. The parties will provide a relative file
15
path or link to the native Excel in the .dat file. The produced file should be named with the Bates
16
number of the first page of the corresponding TIFF production of the document (e.g.,
17
“ABC00001.xls”).
18
E.
Special File Types. If production in native format is necessary to decipher the
19
meaning, context, or content of a document produced in TIFF, the producing party will honor
20
reasonable requests made in good faith for either the production of the original document for
21
inspection and copying or production of the document in native format. Documents that are to be
22
produced in a native format, but that require redactions will be produced as TIFF images with the
23
relevant portions redacted, or if a TIFF image production is not practicable (e.g., the file is a video or
24
very large spreadsheet), as a copy of the native file with the relevant portions replaced with
25
“[REDACTED]” or a similar mark. The produced file should be named with the Bates number of
26
the first page of the corresponding TIFF production of the document (e.g., “ABC00001.ppt”).
27
28
F.
Production of Physical Documents.
Documents or records which either were
originally generated as or converted into ESI but now only exist in physical hard-copy format, or
4
STIPULATION CONCERNING THE PROTOCOL
FOR PRODUCTION OF DOCUMENTS
CASE NO. 12-CV-02907-SC
1
documents or records that were originally generated in hard-copy format, shall be converted to
2
single page image files (BLACK AND WHITE Group IV TIFF) and produced following the same
3
protocols set forth herein or otherwise agreed to by the parties. All such documents will be produced
4
with an OCR file as outlined in Section 7.H. below.
5
G.
Document Unitization. For files produced as either BLACK AND WHITE Group
6
IV TIFF, each page of a document shall be electronically saved as an image file. If a document
7
consists of more than one page, the unitization of the document and any attachments and/or affixed
8
notes shall be maintained as it existed in the original when creating the image files.
9
10
11
H.
The producing party shall produce a Load/Unitization file for all produced documents
in accordance with the following formatting:
OCR and Extracted Text Files (.TXT Files):
12
ESI shall be produced with multi-page searchable Extracted Text or OCR text.
13
documents that were originally stored as native electronic files and which do not have redactions, the
14
extracted, full text from the body of each document will be produced. For documents that were
15
originally stored as native electronic files and which have redactions, OCR text will be produced
16
from the redacted image(s) associated with each document. Any such Extracted Text or OCR will
17
be produced on a document level in the following format:
18
Produce a single text file per document containing all the document's pages
19
For
Filenames must be matched bates number in this form:
20
.txt
21
Where is the BATES number of the first page in the document.
22
Text must be encoded in UTF-8.
23
Text files will be located in a directory named “TEXT” that is separate from the TIFF
24
image.
25
Images Files:
26
Single page per image
27
Black and White Group IV TIFF
28
Filenames for images must be matched bates number in this form:
5
STIPULATION CONCERNING THE PROTOCOL
FOR PRODUCTION OF DOCUMENTS
CASE NO. 12-CV-02907-SC
1
.
2
Where is the BATES number of the page, and is the appropriate
3
extension for the image format (.jpg, .tif).
4
Load/Unitization Files:
5
”Concordance Default” delimited text file utilizing the following characters:
6
The “comma” delimiter is “” (020)
7
The “quote” delimiter is “þ” (254)
8
The “new line” delimiter is “®” (174)
9
First line must contain the column/field names (set forth in Paragraph 1(c) herein)
10
Every row must have the same number of columns/fields (empty values are
11
acceptable)
12
Text must be encoded in UTF-8
13
LFP IPRO LOAD FILE with relative pathing to the image files or OPT OPTICON
14
LOAD FILE with relative pathing to the images files in the format preferable to the
15
Receiving Party
16
Notwithstanding the foregoing, the parties agree to further meet and confer, as necessary, in advance
17
of any production of documents, and in consultation with their respective vendors, to confirm all
18
Load/Unitization file specifications.
19
20
21
I.
De-Duplication. The parties will perform duplicate consolidation as outlined above,
producing a single unique copy of a given e-mail message and its attachments, or standalone file.
J.
Production Media. Documents shall be produced on CD-ROM, DVD, external hard
22
drive (with standard PC compatible interface), .ftp site, or such other readily accessible computer or
23
electronic media as the parties may hereafter agree upon (the “Production Media”). Each item of
24
Production Media shall include: (1) the production date, and (2) the Bates number range of the
25
materials contained on such Production Media item.
26
K.
Document Metadata. Produce extracted metadata for each document in the form of
27
a .dat file, and include the following fields, as shown in the table below. If specific fields cannot be
28
provided for a particular document because, e.g., the field is unavailable or contains privileged
6
STIPULATION CONCERNING THE PROTOCOL
FOR PRODUCTION OF DOCUMENTS
CASE NO. 12-CV-02907-SC
1
information, the field should be left blank. When a metadata field includes a date, the date shall be
2
provided in the following format in separate fields as specified below: mm/dd/yyyy or HH:mm:ssZ.
3
4
5
6
7
8
Field
Bates_Begin
Bates_End
Attach_Begin
Attach_End
File Name
Custodian
Filename Extension
9
11
Subject
Sent_Date
Sent_Time
Create_Date
12
Create_Time
13
Modified_Date
14
Modified_Time
15
Author
From
To
10
16
17
18
CC
BCC
19
MD5/SHA-1
20
Native_File
21
AEO Conf_Desig
22
23
24
Description
The Bates label of the first page of the document.
The Bates label of the last page of the document.
The Bates label of the first page of a family of documents
(e.g., email and attachment).
The Bates label of the last page of a family of documents
(e.g., email and attachment).
The filename of an attachment or stand-alone e-file.
The custodian(s) of the document.
The original filename extension suffix (e.g., .doc, .pps.,
.jpeg, .txt, .xls).
The subject of an email.
For email, the sent date of the message.
For email, the sent time of the message.
For efiles or attachments, the document’s creation date or
operating system creation date.
For efiles or attachments, the document’s creation time
or operating system creation time.
For efiles or attachments, document’s last modified date
or operating system last modified date.
For efiles or attachments, the document’s last modified
time or operating system last modified time.
The author of a stand-alone efile or attachment.
The sender of an email message
The recipients of an email message, in a semi-colon
delimited multi-value list.
The copyee(s) of an email message, in a semi-colon
delimited multi-value list.
The blind copyee(s) of an email message, in a semi-colon
delimited, multi-value list.
The calculated MD5 or SHA-1 hash value of the
document
The file path to the location of the native file if produced
natively.
The confidentiality designation, if any, for the document
pursuant to any protective order in the case.
Production Volume
Name
Deduplicate Custodians Identify all custodians who had an ESI copy of the
produced document in list form separated by commas.
25
Notwithstanding the foregoing, the parties will meet and confer in good faith as necessary prior to
26
the production of documents, with technical experts as needed, to clarify or resolve any issues (e.g.,
27
definitions of metadata fields, inconsistencies, and burden) concerning the production of metadata.
28
7
STIPULATION CONCERNING THE PROTOCOL
FOR PRODUCTION OF DOCUMENTS
CASE NO. 12-CV-02907-SC
1
2
L.
Attachments. Email attachments must be mapped to their parent by the Document or
Production number. BeginAttach and EndAttach fields must be populated for parent documents.
3
M.
Structured Data. To the extent a response to discovery requires production of
4
discoverable electronic information contained in a database, in lieu of producing the database, the
5
parties may meet and confer, with an understanding of which fields are relevant, to attempt to agree
6
upon the sets of data or fields to be included and generate a report in a reasonably usable and
7
exportable electronic file (e.g., Excel or CSV format) for review by the requesting party or counsel.
8
Upon review of the report(s), the requesting party may make reasonable requests for additional
9
information to explain the database schema, codes, abbreviations, and different report formats or to
10
request specific data from identified fields. The parties reserve all rights to object, including but not
11
limited to objections for relevance, undue burden, and/ or inaccessibility.
12
8.
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
PHASING
The parties agree to meet and confer about the propriety of phasing any aspects of ESI
discovery and, if necessary, the timing of any such phasing.
9.
DOCUMENTS PROTECTED FROM DISCOVERY
(a) Pursuant to Fed. R. Evid. 502(d), the production of a privileged or work-productprotected document, whether inadvertent or otherwise, is not a waiver of privilege or
protection from discovery in this case or in any other federal or state proceeding. For
example, the mere production of privileged or work-product-protected documents in this
case as part of a mass production is not itself a waiver in this case or in any other federal
or state proceeding.
(b) The parties have agreed upon a “quick peek” process pursuant to Fed. R. Civ. P. 26(b)(5)
and 26(f)(3)(D) and reserve their rights to assert privilege as follows:
The Producing Party notifies the Receiving Party in writing within ten business days
after discovery of an inadvertent production or disclosure. Such inadvertently
produced or disclosed documents or information, including all copies thereof, shall be
returned to the Producing Party immediately upon request, and the Receiving Party
shall immediately destroy any notes or other writing or recordings that summarize,
reflect, or discuss the content of such privileged or Protected Information. No use
shall be made of such documents or information during deposition or at trial, nor shall
such documents or information be provided to anyone who did not already have
access to them prior to the request by the Producing Party that they be returned. In
the case of an inadvertently produced or disclosed document, the Producing Party
shall include the Discovery material in a privilege log identifying such inadvertently
produced or disclosed document. The Receiving Party may move the Court for an
Order compelling production of any inadvertently produced or disclosed document or
information, but the motion shall not assert as a ground for production the fact of the
inadvertent production or disclosure, nor shall the motion disclose or otherwise use
8
STIPULATION CONCERNING THE PROTOCOL
FOR PRODUCTION OF DOCUMENTS
CASE NO. 12-CV-02907-SC
1
the content of the inadvertently produced document or information (beyond any
information appearing on the above-referenced privilege log) in any way in
connection with any such motion.
(c) Communications involving trial counsel that post-date the filing of the complaint need
not be placed on a privilege log. Communications may be identified on a privilege log by
category, rather than individually, if appropriate.
2
3
4
5
6
7
8
10.
MODIFICATION
This Stipulated Order may be modified by a Stipulated Order of the parties or by the Court
for good cause shown.
IT IS SO STIPULATED, through Counsel of Record.
9
10
Dated: February 14, 2013
11
s/Jonathan D. Brightbill via email consent
Jonathan D. Brightbill
KIRKLAND & ELLIS LLP
Attorneys for Defendant
ZONEPERFECT NUTRITION COMPANY
12
13
15
s/Joseph N. Kravec, Jr.
Joseph N. Kravec, Jr.
STEMBER FEINSTEIN DOYLE PAYNE & KRAVEC, LLC
16
Attorneys for Plaintiff
KIMBERLY S. SETHAVANISH
14
Dated: February 14, 2013
17
18
19
PURSUANT TO STIPULATION, IT IS SO ORDERED.
20
21
February 20
Date: _________________, 2013
_______________________________
The Honorable Samuel Conti
United States District Judge
22
23
24
25
26
27
28
9
STIPULATION CONCERNING THE PROTOCOL
FOR PRODUCTION OF DOCUMENTS
CASE NO. 12-CV-02907-SC
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?