TPOV Enterprises 16, LLC v. Paris Las Vegas Operating Company, LLC
Filing
27
ORDER Granting 26 Stipulated Protocol Governing Production of Electronically Stored Information. Signed by Magistrate Judge Cam Ferenbach on 5/25/17. (Copies have been distributed pursuant to the NEF - ADR)
1
7
James J. Pisanelli, Esq., Bar No. 4027
JJP@pisanellibice.com
Debra L. Spinelli, Esq., Bar No. 9695
DLS@pisanellibice.com
M. Magali Mercera, Esq., Bar No. 11742
MMM@pisanellibice.com
Brittnie T. Watkins, Esq., Bar No. 13612
BTW@pisanellibice.com
PISANELLI BICE PLLC
400 South 7th Street, Suite 300
Las Vegas, Nevada 89101
Telephone:
702.214.2100
Facsimile:
702.214.2101
8
Counsel for Paris Las Vegas Operating Company, LLC
2
3
4
5
6
9
UNITED STATES DISTRICT COURT
10
DISTRICT OF NEVADA
PISANELLI BICE
400 SOUTH 7TH STREET, SUITE 300
LAS VEGAS, NEVADA 89101
11
TPOV ENTERPRISES 16, LLC, a Delaware
Limited Liability Company,
12
13
14
15
16
CASE NO. 2:17-cv-00346-JCM-VCF
Plaintiff,
STIPULATED PROTOCOL GOVERNING
PRODUCTION OF ELECTRONICALLY
STORED INFORMATION
vs.
PARIS LAS VEGAS OPERATING
COMPANY, LLC, a Nevada limited liability
company,
Defendant.
17
18
19
COME NOW, TPOV Enterprises 16, LLC ("TPOV 16"), by and through its undersigned
20
counsel of record, and Defendant Paris Las Vegas Operating Company, LLC ("Paris"), by and
21
through its undersigned counsel of record, and hereby enter into this Stipulated Protocol
22
Governing Production of Electronically Stored Information ("Protocol"). In this Stipulation,
23
TPOV 16 and Paris are collectively referred to as the "Parties" and individually as a "Party."
24
The Parties agree that good cause exists to create a protocol to govern the production of
25
documents and Electronically Stored Information. Thus, the Parties have agreed and stipulated
26
to the entry of this Protocol to ensure efficient production of documents during the pendency of
27
this case.
28
1
1
It is hereby stipulated and agreed, by and between the Parties hereto, through their
2
respective counsel of record, that the production of ESI shall be governed by the following
3
protocol. The Parties are in possession of ESI that may be produced in this matter and the Court
4
hereby orders as follows regarding the production of ESI:
5
1.
Definitions: In this Protocol, the following terms have the following meanings:
6
a. "ESI" means Electronically Stored Information, including, but not limited to,
7
email, attachments to email, other electronic documents such as word processing,
8
spreadsheet, PowerPoint, HTML, and text files and any other files stored in an
9
electronic format.
b. "Metadata" means: (i) information embedded in a Native Format file that is not
11
PISANELLI BICE
400 SOUTH 7TH STREET, SUITE 300
LAS VEGAS, NEVADA 89101
10
ordinarily viewable or printable from the application that generated, edited or
12
modified such Native Format file; and (ii) information generated automatically by
13
the operation of a computer or other information technology system when a Native
14
Format file is created, modified, transmitted, deleted or otherwise manipulated by
15
a user of such system. Metadata is a subset of ESI.
16
c. "Native Format" means ESI in the electronic format of the application in which
17
18
such ESI is normally created, viewed, and/or modified.
2.
Scope: This Protocol shall govern only the actual production of ESI and shall in
19
no way affect the Parties' respective rights and obligations concerning the preservation, collection,
20
and review of ESI. All Parties preserve their attorney-client privileges and other privileges, and
21
there is no intent by this Protocol, or the production of documents pursuant to this Protocol, to in
22
any way waive or weaken these privileges. Nothing in this Protocol shall limit the Parties'
23
respective rights and obligations concerning confidential, proprietary, or private information, with
24
respect to which they may make such agreements or stipulations as they see fit, subject to
25
applicable law. All documents produced pursuant to this Protocol are fully protected and covered
26
by the Parties' confidentiality agreements, and orders of the Court, as well as any clawback
27
agreements, and protective order(s) of the Court effectuating the same.
28
2
1
3.
ESI Production Format:
ESI shall be produced primarily as single-page,
uniquely and sequentially numbered CCITT Group IV TIFF (black and white) image files not less
3
than 300 dpi. Only after receiving the advance permission of the receiving Party, the following
4
additional formats may also be acceptable to represent particular ESI or documents: JPEG,
5
JPEG2000, GIF, PNG, and BMP. The images shall be accompanied by searchable text files
6
containing all extracted text on a document basis, or if extracted text is unavailable (e.g., image
7
PDF files), then searchable text generated using Optical Character Recognition ("OCR") will be
8
provided. The text files shall be named to match the endorsed number assigned to the image of
9
the first page of the document. The images and text files shall also be accompanied by a cross-
10
reference load file. The producing Party shall also provide a data load file ("Data Load File") that
11
PISANELLI BICE
400 SOUTH 7TH STREET, SUITE 300
LAS VEGAS, NEVADA 89101
2
shall contain the agreed-upon coding and/or Metadata, as reasonably available, associated with
12
each field as specified in Schedule A hereto. Data Load Files will be provided in Concordance
13
DAT file format, with field name headers and standard Concordance delimiters. The Image Load
14
File will be provided in the OPT and LFP file formats.
15
4.
Email Production Format:
Email, together with all attachments, shall be
16
produced as follows: as single-page TIFF images representing the pages of emails that would
17
have been viewable in the ordinary course of business prior to collection. Each such TIFF image
18
will show the endorsed document number and confidentiality status for each such email page.
19
The parties will provide the Metadata fields available for emails as identified on Schedule A.
20
5.
Paper Production Format: Documents stored in paper form in the ordinary
21
course of business shall be converted to electronic form and produced as single-page, uniquely
22
and sequentially numbered CCITT Group IV TIFF image files not less than 300 dpi resolution to
23
enable the generation of searchable text using OCR. The images shall be accompanied by text
24
files containing the OCR-generated searchable text. The text files shall be named to match the
25
endorsed number assigned to the image of the first page of the document. The images shall also
26
be accompanied by an image cross-reference load file, providing the beginning and ending
27
endorsed number of each document and the number of pages it comprises. The producing Party
28
3
1
shall also provide a Data Load File corresponding to the CCITT Group IV TIFF image files that
2
shall contain the Metadata fields defined in Schedule A hereto.
3
6.
Bates Numbering for TIFF Images: Each page of a document produced in TIFF
4
file format shall be endorsed with a legible, unique numeric identifier ("Bates Number") not less
5
than eight (8) digits (with zero-padding) electronically "burned" onto the image at a place on the
6
document that does not obscure, conceal, or interfere with any information originally appearing
7
on the document. The Bates Number for each document shall be created so as to identify the
8
producing Party or non-party and the unique document number (e.g., "ABC00000001").
9
7.
Document Unitization: If a paper document is more than one page, to the extent
possible, the unitization of the document and any attachments and/or affixed notes shall be
11
PISANELLI BICE
400 SOUTH 7TH STREET, SUITE 300
LAS VEGAS, NEVADA 89101
10
maintained as it existed when collected by the Parties. If unitization cannot be maintained, the
12
original unitization shall be documented in a load file or otherwise electronically tracked. For
13
ESI, all unitization should be defined within the Data Load File including the designation of
14
parent/attachments both for email and attachments.
15
8.
Color Documents: If the receiving Party believes that a document is not legible
16
or where the absence of color materially affects the document, the receiving Party may request
17
that the document be produced in color, and the Parties shall meet and confer as to the possibility
18
of rendering the document in color format.
19
9.
Production of ESI in Native Format: Other than as specifically set forth below,
20
a producing Party need not produce documents in Native Format. Any Native Format files that
21
are produced should be produced with a link in the "NativeFile" Metadata field, along with all
22
extracted text and Metadata fields set forth in Schedule A hereto. No document produced in
23
Native Format shall be intentionally manipulated to change the appearance or substance of the
24
document prior to its collection or production. All redactions of ESI will be performed on a
25
TIFF-imaged version of the document only, and Native Format files and extracted text will not be
26
provided. Redactions on grounds of attorney-client privilege or attorney work product shall be
27
logged on a privilege log. Redacted ESI will be OCRed to include all visible (non-redacted) text.
28
Any Metadata fields that contain information subject to redaction shall not be produced, however,
4
1
the remainder of the Metadata fields for that document that are not subject to redaction will be
2
produced.
3
production of documents in Native Format in the future should the need to do so arise. Should
4
such need arise, the Parties will meet and confer concerning production of any discovery
5
materials in Native Format.
6
production of discovery materials in Native Format, they shall promptly bring such matter to the
7
Court's attention.
8
10.
Notwithstanding the foregoing, the Parties hereby reserve their rights to request
If the Parties are not able to reach agreement concerning the
Spreadsheets: Subject to the redaction provisions of ¶ 9, spreadsheets (e.g., Excel
and Excel-type files) shall be produced in their Native Format with a link in the NativeFile
10
Metadata field, along with extracted text. For extracted text, the producing Party may need to
11
PISANELLI BICE
400 SOUTH 7TH STREET, SUITE 300
LAS VEGAS, NEVADA 89101
9
unhide all rows and columns depending on what method is being used to extract text.
12
11.
Media Files: All non-privileged video, animation, or audio files shall be produced
13
in their Native Format. All video, animation, or audio files that a producing Party in good faith
14
believes contains material protected by either the attorney-client privilege or attorney work
15
product doctrine must be identified on a privilege log in the form agreed to by the Parties.
16
12.
Other File Types: In some cases it may be necessary to produce documents in
17
their Native Format because such documents cannot be rendered into TIFF format. In other cases,
18
it may be necessary to alter a native file to create a format suitable for production purposes (e.g.,
19
Lotus Notes objects, compiled web pages, etc.). If alteration of a Native Format file is necessary
20
to create a format suitable for production, the Parties will discuss and agree upon an acceptable
21
format.
22
13.
Specific Requests for Production of ESI in Native Format: Other than the
23
specific file types described above, after initial production of ESI in TIFF format, a Party must
24
make a showing of good cause demonstrating particularized need for production of other ESI in
25
its Native Format. In the event that a receiving Party requests production of Native Format ESI,
26
the Parties shall negotiate in good faith about the timing, cost, and method of such production.
27
28
14.
De-Duplication of Non-Emails: All non-email documents will be de-duplicated
across Custodians prior to production, with an "AllCustodians" Metadata field identifying all the
5
1
custodians who possessed copies of the documents. "De-duplicated across Custodians" means
2
that exact duplicates of documents (where the document family is identical), as identified by MD5
3
hash value, will not be produced.
4
15.
De-Duplication of Emails:
For emails, in addition to de-duplication across
custodians, thread de-duplication may be applied prior to production. Thread de-duplication
6
allows emails that are wholly contained in a later, surviving email, with all of the recipients and
7
attachments contained, to be identified and suppressed from production. An email is only
8
removed from production if 100% of the message body is contained, all addresses are included,
9
and all attachments are included in a later email that is produced. When the latest version of an
10
email thread is considered privileged and withheld from production, the Parties are obligated to
11
PISANELLI BICE
400 SOUTH 7TH STREET, SUITE 300
LAS VEGAS, NEVADA 89101
5
"re-thread" the most complete non-privileged earlier emails in the thread and produce such non-
12
privileged emails.
13
16.
De-Nisting of ESI: The Parties may remove operating system files and program
14
files with the assistance of their respective Information Technology vendors prior to conducting
15
searches of such data in accordance with the National Software Reference Library De-Nisting
16
Process.
17
17.
Placeholders: In the event that any production contains documents that could not
18
be rendered to TIFF, the producing Party will insert a numbered TIFF format placeholder page as
19
a replacement for, and to identify, any document that could not be rendered to TIFF or produced
20
for some other reason.
21
Rendered." Any file produced in its Native Format will be produced with an associated TIFF
22
format placeholder with the text "Document Produced in Native Format."
23
18.
The placeholder page(s) will bear the text "Document Cannot Be
Production Media: The Parties will produce document images, Native Format
24
files, load files, and Metadata as encrypted data on DVD-ROM optical discs for Windows-
25
compatible personal computers, Windows-compatible external hard drive employing the USB 2.0
26
interface, or other mutually agreeable media or via an FTP site. The Parties will meet and confer
27
concerning the appropriate process for doing so.
28
6
1
19.
Original Documents: Nothing in this Protocol shall eliminate or alter any Party's
2
obligation to retain Native Format copies, including associated Metadata, of all ESI produced in
3
this matter and original hard copy documents for all paper documents produced in the matter.
4
20.
Third-Party Software: To the extent that documents produced pursuant to this
5
Protocol cannot be rendered or viewed without the use of proprietary third-party software, the
6
Parties shall meet and confer to minimize any expense or burden associated with the production
7
of such documents in an acceptable format, including issues as may arise with respect to
8
obtaining access to any such software and operating manuals which are the property of a third
9
party.
10
PISANELLI BICE
400 SOUTH 7TH STREET, SUITE 300
LAS VEGAS, NEVADA 89101
11
21.
a. For Excel or other spreadsheet files that must be produced in TIFF image
13
format for redactions, hidden columns, and rows shall be made visible.
14
b. PowerPoint documents must be processed with hidden slides and speaker's
15
17
18
The Parties shall use the following specifications
when converting ESI from its Native Format into TIFF image files prior to its production:
12
16
Processing Specifications:
notes unhidden.
The foregoing provisions do not in any way limit a producing Party's ability to make any
necessary redactions, whether for privilege, confidentiality, and/or privacy.
22.
Production Specifications: All documents will be produced according to the
19
following Production Specifications.
20
a. Data Load Files:
21
22
23
24
25
26
27
28
i. Concordance (DAT, OPT, LFP):
1. Version 10 for Unicode support.
ii. DAT file:
1. UTF-8 encoded Unicode to support foreign language.
iii. Fields available in the DAT file (with standard Concordance
delimiters):
1. See Schedule A for list of fields.
iv. Text files will not be provided within the DAT file.
7
1
b. TIFF Specifications:
2
i. Black and white.
3
ii. Single page.
4
iii. CCITT Group IV FAX Compression.
5
iv. 300 dots per inch.
c. Native Format Specifications: Prior to production, Native Format documents
7
will be renamed with their appropriate Bates Numbers (as assigned to the
8
corresponding placeholder) and confidentiality designation in the filename
9
(e.g., "Bates Number_confidentiality designation.file extension"), and a
10
corresponding TIFF format placeholder bearing the text "Document Produced
11
PISANELLI BICE
400 SOUTH 7TH STREET, SUITE 300
LAS VEGAS, NEVADA 89101
6
in Native Format."
12
d. Endorsements:
13
i. Printed with a font size comparable to 10-point Arial.
14
ii. Right footer: Bates Number.
15
iii. Left Footer: Confidentiality legend.
16
1. Legend values:
17
a. HIGHLY CONFIDENTIAL
18
b. CONFIDENTIAL
19
iv. Redactions: White redactions with a border.
20
1. Redaction types:
21
a. Privilege.
22
b. Privacy.
23
c. Personnel issues.
24
d. Regulatory compliance issues.
25
e. Trade secrets and confidential information that would be
26
27
28
protected under the Nevada Uniform Trade Secrets Act.
f. Other.
2. Redaction labels:
8
1
a. REDACTED – PRIVILEGE
2
b. REDACTED – PRIVACY
3
c. REDACTED – PERSONNEL
4
d. REDACTED – COMPLIANCE
5
e. REDACTED – OTHER
6
7
8
9
10
PISANELLI BICE
400 SOUTH 7TH STREET, SUITE 300
LAS VEGAS, NEVADA 89101
11
e. Text Files:
i. One Unicode text file will be provided per document (named according
to the beginning Bates Number for each document).
ii. Text will be extracted from Native Format files when possible.
iii. Text will be provided with scanned documents where such text can be
obtained through OCR.
12
iv. Text files will not contain page breaks.
13
v. Placeholders (with the exception of placeholders for files produced in
14
Native Format) will receive a text file matching the placeholder text.
15
vi. Text files for redacted documents will be created from the redacted
16
17
18
19
20
21
22
23
24
25
image.
vii. OCR text will be provided for documents where text cannot be
extracted.
viii. Text files will support foreign characters for upload into Concordance
Version 10.
f. Sorting:
i. Keep source/attachments (families) together.
g. Data Organization:
i. Images: 1000 TIFF files per folder; no more than 1000 subfolders per
folder; root folder named "Images."
26
ii. Text files: Will reside in a separate folder named "Full_Text."
27
iii. Native Format files: Will reside in a separate folder named "Natives."
28
iv. Data Load Files: Will reside in the root folder.
9
1
2
23.
Embedded Objects:
Embedded objects within files will be extracted and
produced as families.
3
24.
Reservation of Rights:
Nothing contained herein, is intended to create a
4
precedent for, or to constitute a waiver or relinquishment of, any Party's objections or arguments
5
pertaining to any potential future ESI production(s). Nothing contained herein constitutes a
6
waiver of any Party's rights or obligations under any law, including but not limited to laws
7
regarding any matter or information that is or may be claimed to be privileged, confidential,
8
proprietary, or otherwise personal or private.
9
25.
Modification: Any agreement between the Parties to depart from the requirements
of this Protocol as between those Parties must be memorialized in writing, signed by counsel for
11
PISANELLI BICE
400 SOUTH 7TH STREET, SUITE 300
LAS VEGAS, NEVADA 89101
10
all Parties to the agreement, and promptly furnished to all Parties via email and U.S. mail. Such
12
agreement does not relieve those Parties of their obligation to other Parties and to the Court
13
pursuant to this Stipulation.
14
26.
Procedure for Amending or Obtaining Relief from the ESI Production
Protocol:
15
16
a. Amendment:
The Parties may, by mutual agreement, develop and employ
17
production protocols which vary from those set forth above. In such an instance,
18
they shall revise this Protocol and submit the new agreement for the Court's
19
approval.
20
b. Relief: Any Party may request relief from any obligation set forth in this Protocol.
21
All such requests shall be in writing and submitted to the Court for consideration,
22
with a copy of the request served to all Parties. Any Party may oppose any request
23
for relief by submitting a written opposition to the Court, with a copy of the
24
opposition served to all Parties, in accordance with LR 7-2.
25
///
26
27
28
10
1
2
27.
Cost Shifting: Each Party expressly reserves the right to petition the Court to shift
the cost of the production of ESI to the requesting Party.
3
4
DATED this 25th day of May 2017.
DATED this 25th day of May 2017.
5
PISANELLI BICE PLLC
CARBAJAL & MCNUTT, LLP
By:
By:
/s/ Matthew Wolf
Dan McNutt, Esq., Bar No. 7815
Matthew Wolf, Esq., Bar No. 10801
CARBAJAL & MCNUTT, LLP
625 S. 8th Street
Las Vegas, Nevada 89101
6
7
8
9
10
PISANELLI BICE
400 SOUTH 7TH STREET, SUITE 300
LAS VEGAS, NEVADA 89101
11
M. Magali Mercera
James J. Pisanelli, Esq., Bar No. 4027
Debra L. Spinelli, Esq., Bar No. 9695
M. Magali Mercera, Esq., Bar No. 11742
Brittnie T. Watkins, Esq., Bar No. 13612
400 South 7th Street, Suite 300
Las Vegas, Nevada 89101
Attorneys for Defendant Paris Las Vegas
Operating Company, LLC
Attorneys for Plaintiff TPOV Enterprises 16,
LLC
12
13
ORDER
14
15
IT IS SO ORDERED.
16
17
18
UNITED STATES MAGISTRATE JUDGE
5-25-2017
DATED:
19
20
21
22
23
24
25
26
27
28
11
1
2
3
Schedule A
Field Name
Description
Required for
Production Begin Bates
Start Bates
All
Production End Bates
End Bates
All
Production Begin Attach
Family Start Bates
All
Production End Attach
Family End Bates
All
Page Count
Number of Attachments
All
Attachment Count
Number of Attachments
All
10
Confidentiality Branding
Confidentiality designation
All
11
Custodian
Duplicate Custodian
Custodian
All Custodian
All
Subject
Author
From
To
CC
BCC
DateSent
DateReceived
Subject
Author
From
To
CC
BCC
Date Email Sent
Date Email Received
E-mail only
4
5
6
7
8
PISANELLI BICE
400 SOUTH 7TH STREET, SUITE 300
LAS VEGAS, NEVADA 89101
9
12
13
14
15
16
17
18
19
20
21
22
23
24
File Name
File Extensions
File Size
DateCreated
DateModified
File Name
File Extensions
File Size
Date file created
Date the file was last
modified/saved
Attachments/loose files
E-mail only
All
All
All
Email only
Email only
Attachments/loose files
Attachments/loose files
Attachments/loose files
Attachments/loose files
Attachments/loose files
Native File
Loading path for any native file
Any documents produced in
Native Format
Text Path
Loading path for any text file
Can indicate if a document is
redacted
Any documents produced
with redactions
25
26
All
Has Redactions
27
28
12
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?