Martinelli v. Johnson & Johnson et al

Filing 28

STIPULATION and ORDER signed by Chief Judge Morrison C. England, Jr., on 4/13/16, ORDERING that the foregoing 26 Stipulation is hereby ADOPTED by the Court and shall govern the production of electronically stored information and paper documents. (Kastilahn, A)

1 TUCKER ELLIS LLP
Mollie F. Benedict - SBN 187084

2 [e-mail]
3 Amanda Villalobos - SBN 262176
4
5
6
7

[e-mail]
515 South Flower Street
Forty-Second Floor
Los Angeles, CA 90071-2223
Telephone:
213.430.3400
Facsimile:
213.430.3409
Attorneys for Defendants JOHNSON & JOHNSON

8 and MCNEIL NUTRITIONALS, LLC

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

9 BURSOR & FISHER, P.A.
L. Timothy Fisher (State Bar No. 191626)
10 Julia A. Luster (State Bar No. 295031)

1990 North California Boulevard, Suite 940

11 Walnut Creek, CA 94596
Telephone: [phone]
12 Facsimile: [phone]
13

E-Mail: [e-mail]
[e-mail]

14 BURSOR & FISHER, P.A.
Scott A. Bursor (State Bar No. 276006)
15 888 Seventh Avenue
New York, NY 10019

16 Telephone: [phone]
Facsimile: [phone]
17 E-Mail: [e-mail]
18 Attorneys for Plaintiff JOANN MARTINELLI
19
20

UNITED STATES DISTRICT COURT

21

EASTERN DISTRICT OF CALIFORNIA

22
23 JOANN MARTINELLI, individually and on
24
25
26

behalf of all others similarly situated,
Plaintiff,
v.

JOHNSON & JOHNSON and McNEIL
27 NUTRITIONALS, LLC,

28

Defendants.

) Case No. 2:15-cv-01733-MCE-EFB
)
) STIPULATED ESI AND HARD COPY
) PROTOCOL
)
)
)
)
)
)
)

STIPULATED ESI AND HARD COPY PROTOCOL

1

The Parties hereby agree to the following protocol for production of electronically stored

2 information (“ESI”) and paper (“hardcopy”) documents. Subject to the agreed upon Protective Orders in
3 this Action, this protocol governs all productions in this action. This protocol has the objective to
4 facilitate the just, speedy, and inexpensive completion of discovery of ESI and hardcopy documents and
5 to promote, whenever possible, the early resolution of disputes, including any disputes pertaining to
6 scope or costs regarding the discovery of ESI without Court intervention. Nothing in this protocol shall
7 limit a party’s right to seek or object to discovery as set out in applicable rules, to rely on any Protective
8 Order entered in this action concerning protection of confidential or otherwise sensitive information, or

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

9 to object to the authenticity or admissibility of any hardcopy document or ESI produced in accordance
10 with this protocol. The mere production of ESI as part of a mass production shall not itself constitute a
11 waiver for any purpose.
12 A.

GENERAL AGREEMENTS

13 1.

Ongoing Cooperation among the Parties

14

The parties are aware of the importance the Court places on cooperation and commit to continue

15 to consult and cooperate reasonably as discovery proceeds. The parties recognize that the failure of
16 counsel or the parties to this action to cooperate in facilitating and reasonably limiting discovery
17 requests and responses raises litigation costs and contributes to the risk of sanctions. The parties agree
18 that their counsel’s zealous representation of them is not compromised by conducting discovery in a
19 cooperative manner.
20 2.

Proportionality

21

a.

Reasonable Discovery Limits. The proportionality standard set forth in Rule 26(b)(2)(C)

22 of the Federal Rules of Civil Procedure (“FRCP”)1 shall apply to discovery in this action. Consistent
23 with that proportionality standard, the parties agree to cooperate in identifying and agreeing to
24 appropriate limits on discovery, including limits on the number of custodians, discoverable data sources,
25 and relevant time periods. The parties shall not be obligated to collect or produce ESI created after the
26 date of filing of the initial complaint in this action.
27

b.

Discoverable Custodians and Non-Custodial Data Sources. Consistent with the

28 proportionality standard, within twenty one (21 )days after the Court’s entry of this protocol, each party
1 Unless otherwise indicated, all statutory references herein are to the FRCP.

2
STIPULATED ESI AND HARDCOPY PROTOCOL

1 shall provide to the other party a list of the party’s twelve (12) most likely custodians, as well as a list of
2 non-custodial data repositories whose reasonably accessible emails and other ESI the party will search
3 for relevant information. Custodians shall be identified by name, title, dates of employment by the
4 party, and a brief description of their employment duties. The parties agree to meet and confer in good
5 faith in order to reach agreement on the lists of custodians whose emails and other ESI will be searched,
6 and to agree upon such list (the “Final Custodian List”) within fourteen (14) days of the date each party
7 receives the other party’s proposed list of twelve (12) most likely custodians. Absent a showing of good
8 cause, and subject to any further agreement among the parties, the list(s) provided pursuant to this

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

9 paragraph shall be the presumptive limit on permissible ESI discovery. If any custodian or data source
10 identified on the Final Custodian List is located outside the United States, the parties shall meet and
11 confer regarding such matters as relevancy and privacy of the data at issue and, as applicable, the timing
12 of production of any such data.
13

c.

Discovery Concerning Preservation and Collection Efforts. Discovery concerning the

14 preservation and collection efforts of another party can contribute to unnecessary expense and delay and
15 may inappropriately implicate work product and attorney-client privileged matters. If there is a dispute
16 concerning the scope of a party’s preservation or collection efforts, the parties or their counsel must
17 meet and confer and fully explain their reason for believing additional efforts are, or are not, relevant
18 and proportional pursuant to Rule 26(b)(1). In particular, before initiating discovery about preservation
19 and collection, a party shall confer with the other party concerning the specific need for such discovery,
20 including its relevance to claims and defenses, and the suitability of alternative means for obtaining the
21 information.
22

d.

On-Site Inspections of ESI. On-site inspections of ESI under Rule 34(b) shall be

23 permitted only upon a good-faith showing by the requesting party of good cause and specific need or
24 upon agreement of the parties. As appropriate, the Court may condition on-site inspections of ESI, as
25 authorized in the preceding sentence, to be performed by independent third-party experts, and the Court
26 may set other conditions it may deem appropriate.
27

e.

Non-Discoverable ESI. Consistent with the proportionality standard set forth in the

28 FRCP, absent a party’s specific written notice for good cause, the following categories of ESI are
presumed to be inaccessible and not discoverable:
3
STIPULATED ESI AND HARDCOPY PROTOCOL

1

i.

2
3

ESI deleted in the normal course of business before the time a preservation
obligation in this action came into effect;

ii.

Backup data files that are maintained in the normal course of business for

4

purposes of disaster recovery, including, but not limited to, backup tapes, disks,

5

SAN, and other forms of media that are substantially duplicative of data that are

6

more accessible elsewhere;

7

iii.

Deleted, “slack,” fragmented, or unallocated data only accessible by forensics;

8

iv.

Random access memory (RAM), temporary files, or other ephemeral data that are

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

9
10

difficult to preserve without disabling the operating system;
v.

11
12

files, cache files, and cookies;
vi.

13
14

On-line access data such as,(without limitation, temporary internet files, history

Data in metadata fields frequently updated automatically, such as last-opened or
last-printed dates;

vii.

Electronic data (e.g., call logs, email, calendars, contact data, notes, and text

15

messages) sent to or from mobile devices (e.g., iPhone, iPad, Android, and

16

Blackberry devices), provided that copies of all such electronic data are routinely

17

saved elsewhere (such as on a server, laptop, desktop computer, or ‘cloud’

18

storage);

19

viii.

Voicemail, including Telephone or VOIP voice messages;

20

ix.

Text messages and instant messages that are not retained in the ordinary course of

21

business;

22

x.

SAS program and data files;

23

xi.

Server, system, network, or software application logs;

24

xii.

Data remaining from systems no longer in use that are unintelligible on the

25
26

systems currently in use;
xiii.

Electronic data temporarily stored by laboratory equipment or attached electronic

27

equipment, provided that such data are not ordinarily preserved as part of a

28

laboratory report; and

4
STIPULATED ESI AND HARDCOPY PROTOCOL

1

xiv.

2

Structural files not material to individual file contents (e.g., .CCS, .XSL, .XML,
.DTD, etc.).

3

f.

Disaster-Recovery Backup Data. Consistent with the proportionality standard of the

4 FRCP, absent a party’s specific written notice for good cause, no party shall be required to modify or
5 suspend procedures, including rotation of backup media, used in the normal course of business to back
6 up data and systems for disaster recovery purposes. Absent a showing of good cause, such backup media
7 shall be considered to be not reasonably accessible. Nothing in this provision obviates a party’s duty to
8 implement a litigation hold.

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

9 3.
10

No Designation of Discovery Requests
Productions of hardcopy documents and ESI in the reasonably usable form set out in this

11 protocol, including Attachment A, need not be organized and labeled to correspond to the categories in
12 the requests.
13 4.

Inadvertent Production

14 The inadvertent production of any emails, ESI, or other material constituting or containing attorney15 client privileged information or attorney work-product, or which constitutes or contains information
16 protected by any applicable privacy law or regulation, shall be governed by provisions contained in the
17 Protective Order previously entered in this action.
18 B.

ELECTRONICALLY STORED INFORMATION

19 1.

Production in Reasonably Usable Form

20

a.

The parties shall produce ESI in reasonably usable form. Except as stated in paragraphs

21 B.2 and B.3 below or as agreed hereafter by the parties, such reasonably usable form shall be the single22 page TIFF-image format with extracted or OCR text and associated metadata as set out in Attachment
23 A, which is incorporated in full into this protocol. If the receiving party for good cause explained in the
24 request seeks production in native format of specifically identified ESI produced originally in TIFF25 image form, the producing party shall respond reasonably and in good faith to any such request.
26

b.

Redactions. The Producing Party may redact from any TIFF image, metadata field, or

27 native file material that is protected from disclosure by applicable privilege or immunity, that is
28 governed by California Civil Code § 1798.1 or that the Protective Order entered in this Action allows to
be redacted.
5
STIPULATED ESI AND HARDCOPY PROTOCOL

1

c.

Each party may make requests for good cause seeking production of specifically

2 identified documents in color.
3 2.

Electronic Spreadsheets, Presentations, Desktop Databases, and Multimedia Files

4

Electronic spreadsheets (e.g., Excel), electronic presentations (e.g., PowerPoint), desktop

5 databases (e.g., Access), and audio/video multimedia files that have been identified as responsive shall
6 be produced in native format, unless they are authorized to be redacted in accordance with Paragraph 1.b
7 above. After such redactions, the producing party either shall produce the redacted file in the reasonably
8 usable form set out in Attachment A or shall produce the redacted copy in native format.

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

9 3.
10

Enterprise Databases and Database Management Systems
In instances in which discoverable ESI in an enterprise database or database management system

11 (e.g., Oracle, SQL server, DB2) can be produced in an already existing and reasonably available report,
12 the parties shall collect and produce, in the reasonably usable TIFF-image form described in Attachment
13 A, the discoverable material in that report format. If an existing report form is not reasonably available,
14 the parties shall export from the original database discoverable information in a format compatible with
15 Microsoft Excel or Microsoft Access, and the information shall be produced in that native format.
16 4.

Additional Procedures for Native Format Files

17

a.

Procedures for assigning production numbers and confidentiality information to files

18 produced in native format are addressed in Appendix A, incorporated herein, at Paragraph A.15.
19

b.

Any party seeking to use, in any proceeding in this action, files produced in native format

20 shall do so subject to the following:
21

i.

If the native file has been converted to TIFF-image or hardcopy, the original

22

production number and confidentiality designation shall be stamped on each page

23

of the resulting TIFF-image or hardcopy document representing the original

24

native-format file, with a suffix added to the production number to identify the

25

particular page in the file (e.g., XYZ00001_001). In addition, the MD5 or SHA-1

26

hash value of the native file from which the TIFF-image or hardcopy document

27

was generated shall be placed on the first page of the TIFF-image or hardcopy

28

document;

6
STIPULATED ESI AND HARDCOPY PROTOCOL

1

ii.

If the file will be used in its native format, the party seeking to use the native file

2

shall first provide to other parties, sufficiently in advance of such use that the

3

producing party can confirm that the file to be used is the same as the file

4

produced, both the production number and the MD5 or SHA-1 hash value of the

5

file; and

6

iii.

Use of a file in native format, or use of a TIFF-image or hardcopy document

the file being used is an accurate and complete depiction of the original native-

9

TUCKER ELLIS LLP

representing the original native-format file shall constitute a representation that

8

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

7

format file.

10 5.

Use of Search Filters

11

a.

To contain costs associated with the identification of relevant ESI for review and

12 production, the parties may meet and confer to discuss either the use of reasonable search terms, file
13 types, and date ranges, or the use of advanced search and retrieval technologies, including predictive
14 coding or other technology-assisted review. The parties agree to meet and confer in good faith to reach
15 agreement on a list of search terms and protocols for the production of ESI. During such discussions,
16 the producing party shall retain the sole right and responsibility to manage and control searches of its
17 data files. If the producing party makes revisions to search terms or advanced technology procedures in
18 order to make them more accurate and cost-effective, the producing party agrees to meet and confer with
19 the requesting party regarding such revisions. A party’s failure to meet and confer or to make a timely
20 request for different or additional searches as described in this paragraph shall waive that party’s right to
21 object to the sufficiency of the searches actually conducted.
22

b.

If, prior to the conduct of any searches, a receiving party believes in good faith that the

23 producing party’s decisions would result in deficiencies in production, the receiving party may make
24 prompt, reasonable requests for different or additional searches. The producing party shall respond
25 reasonably to such requests. Any proposed search terms shall be narrowly tailored to particular a issue.
26 Indiscriminate terms, such as the producing party’s name or its product names, are inappropriate unless
27 combined with narrowing search criteria that sufficiently reduce the risk of over-inclusion.
28

c.

The fact that any electronic file has been identified in agreed-upon searches shall not

prevent any party from withholding such file from production on the ground that it is protected from
7
STIPULATED ESI AND HARDCOPY PROTOCOL

1 disclosure by applicable privilege or immunity, that is protected from disclosure by California Civil
2 Code § 1798.1 or that the Protective Order entered in this Action allows to be withheld.
3

d.

Nothing in this section shall limit a party’s right to seek reasonably agreement from the

4 other parties or a Court ruling to modify previously agreed-upon search terms or procedures for
5 advanced search and retrieval technologies.
6

e.

The producing party shall propose an initial list of search terms to the requesting party.

7 The parties agree to meet and confer in good faith to finalize a list of acceptable search terms within
8 sixty (60) days of finalizing the Final Custodian List. Should the parties be unable to resolve any

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

9 disputes cooperatively, they shall promptly bring their unresolved dispute(s) to the Court’s attention.
10

f.

The parties agree that a “hit” on a search term is not the sole factor in determining

11 whether ESI is responsive to party’s requests for production. For the avoidance of doubt, the producing
12 party is not required to produce ESI containing a search term if the ESI is not otherwise responsive to a
13 party’s requests for production in this action, if it is protected from disclosure by applicable privilege, or
14 that the Protective Order entered in this action allows the ESI to otherwise be withheld. The parties
15 further agree that ESI that does not contain a “hit” on a search term may be excluded from production.
16 6.

Email Threading

17

a.

Email threads are email communications that contain prior or lesser-included email

18 communications that also may exist separately in the party’s electronic files. A most inclusive email
19 thread is one that contains all of the prior or lesser-included emails, including attachments, for that
20 branch of the email thread. The parties agree that removal of wholly-included, prior-in-time, or lesser21 included versions from potential production will reduce all parties’ costs of document review,
22 production, and litigation-support hosting. Accordingly, each party may produce or list on any required
23 privilege log only the most inclusive email threads.
24

b.

Following production of the most inclusive email threads, and for good cause, a receiving

25 party may make reasonable requests, with respect to most-inclusive email threads particularly identified
26 in the requests, for metadata associated with individual prior or lesser-included emails within the
27 identified most inclusive email threads. Upon such request, the producing party shall cooperate
28 reasonably in responding to any such requests.
7.

Avoidance of Duplicate Production
8
STIPULATED ESI AND HARDCOPY PROTOCOL

1

“Duplicate ESI” means files that are exact duplicates based on the files’ MD5 or SHA-1 hash

2 values. The producing party need produce only a single copy of responsive Duplicate ESI. A producing
3 party shall take reasonable steps to de-duplicate ESI globally (i.e., both within a particular custodian’s
4 files and across all custodians). Entire document families may constitute Duplicate ESI. De-duplication
5 shall not break apart families. When the same Duplicate ESI exists in the files of multiple custodians,
6 those persons shall be listed in the Custodian field identified in Paragraph A.14(c) of Attachment A.
7 C.

DOCUMENTS THAT EXIST ONLY IN HARDCOPY (PAPER) FORM

8

A party may produce documents that exist in the normal course of business only in hardcopy

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

9 form either (a) in their original hardcopy form, or (b) scanned and produced, with Bates numbers added
10 and redacted as necessary in accordance with the procedures set out in Attachment A. Except as set out
11 in section A.4 above, the scanning of original hardcopy documents does not otherwise require that the
12 scanned images be treated as ESI.
13 DATED: April 8, 2016

TUCKER ELLIS LLP

14
15

By:

16
17
18
19
20
21

/s/ Amanda Villalobos
Mollie F. Benedict - SBN 187084
[e-mail]
Amanda Villalobos - SBN 262176
[e-mail]
515 South Flower Street
Forty-Second Floor
Los Angeles, CA 90071-2223
Telephone:[phone]
Facsimile: 213.430.3409
Attorneys for Defendants MCNEIL
NUTRITIONALS, LLC and JOHNSON &
JOHNSON

22
23
24
25
26
27
28
9

STIPULATED ESI AND HARDCOPY PROTOCOL

1
2

DATED: April 8, 2016

BURSOR & FISHER, P.A.

3
By:

4
5
6
7
8

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

9

/s/ Julia A. Luster
L. Timothy Fisher - SBN 191626
[e-mail]
Julia A. Luster - SBN 295031
[e-mail]
1990 North California Blvd., Suite 940
Walnut Creek, CA 94596
Telephone:[phone]
Facsimile: 925.407.2700
Attorneys for Plaintiff JOANN
MARTIENLLI

10
11
12

ORDER

13
14

The foregoing stipulation is hereby adopted by the Court and shall govern the production of

15 electronically stored information and paper documents.
16

IT IS SO ORDERED.

17 Dated: April 13, 2016
18
19
20
21
22
23
24
25
26
27
28
10
STIPULATED ESI AND HARDCOPY PROTOCOL

1
2

ATTACHMENT A
A1.

Image Files. Files produced in *.tif format will be single page black and white *.tif

3 images at 300 DPI, Group IV compression. To the extent possible, original orientation will be
4 maintained (i.e., portrait-to-portrait and landscape-to-landscape). Each *.tif image will be assigned a
5 unique name matching the production number of the corresponding page. Such files will be grouped in
6 folders of no more than 1,000 *.tif files each unless necessary to prevent a file from splitting across
7 folders. Files will not be split across folders and separate folders will not be created for each file.
8 Production (“Bates”) numbers shall be endorsed on the lower right corner of all images. This number
9 shall be a unique, consistently formatted identifier that will:

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

10

a.

be consistent across the production;

11

b.

contain no special characters; and

12

c.

be numerically sequential within a given file.

13

Bates numbers should be a combination of an alpha prefix along with an 8 digit number (e.g.

14 ABC00000001). The number of digits in the numeric portion of the Bates number format should not
15 change in subsequent productions. Confidentiality designations, if any, will be endorsed on the lower
16 left corner of all images and shall not obscure any portion of the original file.
17

A2.

File Text. Except where ESI contains text that has been redacted under assertion of

18 privilege or other protection from disclosure, full extracted text will be provided in the format of a single
19 *.txt file for each file (i.e., not one *.txt file per *.tif image). Where ESI contains text that has been
20 redacted under assertion of privilege or other protection from disclosure, the redacted *.tif image will be
21 OCR’d and file-level OCR text will be provided in lieu of extracted text. Searchable text will be
22 produced as file-level multi-page UTF-8 text files with the text file named to match the beginning
23 production number of the file. The full path of the text file must be provided in the *.dat data load file.
24 The text file shall include interlineated image keys/bates numbers sufficient to show, for all TIFF-image
25 pages, the bates-numbered page of the associated text.
26

A3.

Word Processing Files. Word processing files, including without limitation Microsoft

27 Word files (*.doc and *.docx), will be produced in the above format with tracked changes, comments,
28 and hidden text showing.

ATTACHMENT A

1

A4.

Presentation Files. To the extent that presentation files, including without limitation

2 Microsoft PowerPoint files (*.ppt and *.pptx), are produced in *.tif image format, such *.tif images will
3 display comments, hidden slides, speakers’ notes, and similar data in such files.
4

A5.

Spreadsheet or Worksheet Files. To the extent that spreadsheet files, including, without

5 limitation, Microsoft Excel files (*.xls or *.xlsx), are produced in *.tif image format, such *.tif images
6 will display hidden rows, columns, and worksheets, if any, in such files.
7

A6.

Parent-Child Relationships. Parent-child relationships (e.g., the associations between

8 emails and their attachments) will be preserved. Email and other ESI attachments will be produced as

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

9 independent files immediately following the parent email or ESI record. Parent-child relationships will
10 be identified in the data load file pursuant to paragraph A.14 below.
11

A7.

Dynamic Fields. Files containing dynamic fields such as file names, dates, and times will

12 be produced showing the field code (e.g., “[FILENAME]” or “[AUTODATE]”), rather than the values
13 for such fields existing at the time the file is processed.
14

A8.

English Language. To the extent any data exists in more than one language, the data will

15 be produced in English, if available. If no English version of a file is available, the producing party shall
16 not have an obligation to produce an English translation of the data.
17

A9.

Embedded Objects. Some Microsoft Office and .RTF files may contain embedded

18 objects. Such objects typically are the following file types: Microsoft Excel, Word, PowerPoint, Project,
19 Outlook, and Access; and PDF. Subject to claims of privilege and immunity, as applicable, objects with
20 those identified file types shall be extracted as separate files and shall be produced as attachments to the
21 file in which they were embedded.
22

A10.

Compressed Files. Compressed file types (i.e., .CAB, .GZ, .TAR. .Z, .ZIP) shall be

23 decompressed in a reiterative manner to ensure that a zip within a zip is decompressed into the lowest
24 possible compression resulting in individual files.
25

A11.

Encrypted Files. The producing party will take reasonable steps, prior to production, to

26 unencrypt any discoverable electronically stored information that exists in encrypted format (e.g.,
27 because password-protected) and that can be reasonably unencrypted.
28

A12.

Scanned Hardcopy Documents
2
ATTACHMENT A

1

a.

In scanning hardcopy documents, multiple distinct documents should not

2

be merged into a single record, and single documents should not be split

3

into multiple records (i.e., hard copy documents should be logically

4

unitized).

5

b.

If a producing party is requested, and agrees, to provide OCR text for

document level and provided in document-level *.txt files named to match

8

the production number of the first page of the document to which the OCR

9

TUCKER ELLIS LLP

scanned images of hard copy documents, OCR should be performed on a

7

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

6

text corresponds. OCR text should not be delivered in the data load file or

10

any other delimited text file.

11

c.

In the case of an organized compilation of separate hardcopy documents—

12

for example, a binder containing several separate documents behind

13

numbered tabs—the document behind each tab should be scanned

14

separately, but the relationship among the documents in the binder should

15

be reflected in proper coding of the family fields set out below.

16

A13.

17

In following the requirements of Paragraph A.1, the producing party shall take reasonable steps

Production Numbering.

18 to ensure that attachments to documents or electronic files are assigned production numbers that directly
19 follow the production numbers on the documents or files to which they were attached. If a production
20 number or set of production numbers is skipped, the skipped number or set of numbers will be noted. In
21 addition, wherever possible, each *.tif image will have its assigned production number electronically
22 “burned” onto the image.
23
24

A14.

Data and Image Load Files.
a.

Load Files Required. Unless otherwise agreed, each production will

25

include a data load file in Concordance (*.dat) format and an image load

26

file in Opticon (*.opt) format.

27

b.

Load File Formats.

28
3
ATTACHMENT A

1

i.

Load file names should contain the volume name of the production

2

media. Additional descriptive information may be provided after

3

the volume name. For example, both ABC001.dat or

4

ABC001_metadata.dat would be acceptable.

5

ii.

Unless other delimiters are specified, any fielded data provided in

6

a load file should use Concordance default delimiters. Semicolon

7

(;) should be used as multi-entry separator.

8

iii.

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

9

the first line a list of the fields provided in the order in which they

10
11

Any delimited text file containing fielded data should contain in

are organized in the file.
c.

Fields to be Included in Data Load File. For all documents or electronic

12

files produced, the following metadata fields for each document or

13

electronic file, if available at the time of collection and processing and

14

unless such metadata fields are protected from disclosure by attorney-

15

client or work-product privilege, or California Civil Code § 1798.1, will

16

be provided in the data load file pursuant to subparagraph (a), above,

17

except to the extent that a document or electronic file has been produced

18

with redactions. The term “Scanned Docs” refers to documents that are in

19

hard copy form at the time of collection and have been scanned into *.tif

20

images. The term “Email and E-Docs” refers to files that are in electronic

21

form at the time of their collection.

22
23
24 / / /
25 / / /
26 / / /
27 / / /
28 / / /
4
ATTACHMENT A

1

Field

Sample Data

Scanned Docs

Email and E-Docs

Comment

ABC00000001

Yes

Yes

Beginning production number

2

PRODBEG
[Key Value]
PRODEND

ABC00000008

Yes

Yes

Ending production number

3

PRODBEGATT

ABC00000009

Yes

Yes

4

PRODENDATT

ABC00001005

Yes

Yes

5

PRODCOUNTATT

2

Yes

Yes

6

CUSTODIAN

Smith, John

Yes

Yes

OTHER_CUSTODIANS

Doe, Jane; Jones,
James

Yes

Yes

NATIVEFILE

N/A

Yes

Beginning production number
of parent in a family
Ending production number of
last page of the last attachment
in a family
The number of attachments
associated with a family
Custodian(s) that possessed the
document or electronic file—
multiple custodians separated
by semicolon
When global de-duplication is
used, these are custodians
whose file has been deduplicated
Path and file name for native
file on production media

N/A

Yes

N/A

Yes

N/A

Yes

7
8

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

9
11

FILEDESC

12

FOLDER

13

FILENAME

Natives\001\001\
ABC
00000001.xls
Microsoft Office
2007 Document
\My
Documents\Docu
ment1.doc
Document1.doc

14

DOCEXT

DOC

N/A

Yes

15

PAGES

2

Yes

Yes

AUTHOR

John Smith

N/A

Yes

DATECREATED

10/09/2005

N/A

Yes

DATELASTMOD

10/09/2005

N/A

Yes

NAMELASTMOD

John Smith

No

Yes

22

SUBJECT

Changes to
Access Database

N/A

Yes

23

FROM

John Beech

N/A

Yes

24

TO

Janice Birch

N/A

Yes

25

CC

Frank Maple

N/A

Yes

26

BCC

John Oakwood

N/A

Yes

27

DATESENT

10/10/2005

N/A

Yes

28

TIMESENT

10:33 am

N/A

Yes

10

16
17
18
19
20
21

5
ATTACHMENT A

Description of the type file for
the produced record.
Original source folder for the
record produced.
Name of original electronic file
as collected.
File extension for email or edoc
Number of pages in the
produced document or
electronic file (not applicable
to native file productions).
Author information as derived
from the properties of the
document.
Date that non-email file was
created as extracted from file
system metadata
Date that non-email file was
modified as extracted from file
system metadata
Last author of non-email file as
extracted from file system
metadata
“Subject” field extracted from
email message or metadata
properties of the document
“From” field extracted from
email message
“To” field extracted from email
message
“Cc” or “carbon copy” field
extracted from email message
“Bcc” or “blind carbon copy”
field extracted from email
message
Sent date of email message
(mm/dd/yyyy format)
Sent time of email message,
time zone set to GMT

1

DATERCVD

10/10/2005

N/A

Yes

2

TIMERCVD

10:33 am

N/A

Yes

3

HASHVALUE

No

Yes

4

e4d909c290d
0fb1ca068ff
addf22cbd0

CONFIDENTIALITY

Yes

Yes

5

TEXTPATH

Yes

Yes

6

PRODVOL

HIGHLY
CONFIDENTIAL
Text\001\001\
ABC00000001.txt
VOL001

Yes

Yes

7

A15.

Received date of email
message (mm/dd/yyyyformat)
Received time of email
message, time zone set to GMT
MD5 or SHA-1 hash value

Text of confidentiality
designation, if any
Path to *.txt file containing
extracted or OCR text
Name of the Production
Volume

Files Produced in Native Format. Any electronic file produced in native file format shall

TUCKER ELLIS LLP

Cleveland ♦ Columbus ♦ Denver ♦ Los Angeles ♦ San Francisco

8 be given a file name consisting of a unique Bates number and, as applicable, a confidentiality
9 designation; for example, “ABC00000002_[Original File Name]_Confidential.” For each native file
10 produced, the production will include a *.tif image slipsheet indicating the production number of the
11 native file and the confidentiality designation, and stating “File Provided Natively”. To the extent that it
12 is available, the original file text shall be provided in a file-level multi-page UTF-8 text file with a text
13 path provided in the *.dat file; otherwise the text contained on the slipsheet shall be provided in the *.txt
14 file with the text path provided in the *.dat file.
15
A16. Production Media. Unless otherwise agreed, documents and ESI will be produced on
16 optical media (CD/DVD), external hard drive, secure FTP site, or similar electronic format. Such media
17 should have an alphanumeric volume name; if a hard drive contains multiple volumes, each volume
18 should be contained in an appropriately named folder at the root of the drive. Volumes should be
19 numbered consecutively (ABC001, ABC002, etc.). Deliverable media should be labeled with the name
20 of this action, the identity of the producing Party, and the following information: Volume name,
21 production range(s), and date of delivery.
22

A17.

Encryption of Production Media. To maximize the security of information in transit, any

23 media on which documents or electronic files are produced may be encrypted by the producing party. In
24 such cases, the producing party shall transmit the encryption key or password to the requesting party,
25 under separate cover, contemporaneously with sending the encrypted media. The receiving parties in this
26 matter are on notice that certain data produced may originate from custodians in the European Union
27 and the receiving parties therefore agree to follow the strictest security standards in guarding access to
28 said data.
6
ATTACHMENT A