`
`
`
`LBT IP I LLC,
`
`
`Plaintiff,
`
`
`
`v.
`
`
`APPLE INC.,
`
`Defendant.
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE DISTRICT OF DELAWARE
`
`
`
`
`
`C.A. No. 19-1245-LPS
`
`
`
`
`
`
`
`
`
`
`STIPULATION AND ORDER
`REGARDING DISCOVERY OF ELECTRONICALLY-STORED INFORMATION
`
`
`Plaintiff LBT IP I LLC and Defendant Apple Inc. (“Defendant”) hereby agree that the
`
`following procedures shall govern discovery of Electronically-Stored Information (“ESI”) in this
`
`case:
`
`1.
`
`Custodian names and search terms to be exchanged. The parties shall meet and
`
`confer to reach agreement on a reasonable list of custodians for purposes of collection, review and
`
`production of electronically stored information. In connection with the meet and confer process,
`
`each party shall provide a proposed list of individual custodians who are knowledgeable about and
`
`were involved with the core issues or subjects in this case (e.g., the asserted patents, the
`
`development, design and operation of the accused products, and sales, marketing and other
`
`damages-related information for the accused products). The parties then shall meet and confer to
`
`reach agreement on document custodians and also shall meet and confer to reach agreement on
`
`search terms to be used for electronic searches of the files from those custodians. ESI, including,
`
`but not limited to electronic files and email, shall be collected for each individual custodian from
`
`the personal computers, network resources, and other electronic devices that those individuals use
`
`for work purposes. Notwithstanding prior agreement on the search terms to be used for electronic
`
`
`
`
`
`Case 1:19-cv-01245-LPS Document 30 Filed 05/01/20 Page 2 of 7 PageID #: 287
`
`
`
`searches, should a search produce an unreasonably large number of non-responsive or irrelevant
`
`results, the parties shall (at the producing party’s request) meet and confer to discuss application
`
`of further negative search restrictions (e.g., if a single search was for “card” and ninety percent of
`
`the resulting documents came from the irrelevant term “credit card,” a negative limitation to ignore
`
`documents only returned as a result of “credit card” may be applied to remove these documents).
`
`The party receiving production shall not unreasonably oppose such further restrictions designed to
`
`filter immaterial search results. The parties shall make good faith efforts to identify appropriate
`
`email custodians and produce email on the agreed upon schedule, but reserve the right to seek
`
`email from additional email custodians identified through discovery.
`
`2.
`
`Format for production of documents – documents existing in electronic
`
`format. Except as otherwise provided for in this Stipulation, all documents existing in electronic
`
`format shall be produced in multiple page, searchable PDF format at a resolution of at least 300
`
`dpi in accordance with the following:
`
`(a)
`
`PDF files shall be produced along with Concordance/Opticon image load
`
`files that indicate the beginning and ending of each document.
`
`(b)
`
`For documents which already exist in PDF format prior to production (i.e.,
`
`which the producing party receives from a client or third party in PDF format), the producing party
`
`may provide them in that same PDF format, whether searchable or non-searchable. For documents
`
`converted to PDF format prior to production, the producing party shall make reasonable efforts to
`
`convert to searchable PDF.
`
`(c) Metadata. Load files should include, where applicable, the information
`
`listed in the Table of Metadata Fields, attached as Exhibit A. However, the parties are not obligated
`
`to include metadata for any document that does not contain such metadata in the original, if it is
`
`not possible to automate the creation of metadata when the document is collected. The parties
`
`2
`
`
`
`Case 1:19-cv-01245-LPS Document 30 Filed 05/01/20 Page 3 of 7 PageID #: 288
`
`
`
`reserve their rights to object to any request for the creation of metadata for documents that do not
`
`contain metadata in the original.
`
`(d)
`
`Production media and encryption of productions. Unless otherwise
`
`agreed, the parties shall provide document productions in the following manner: The producing
`
`party shall provide the production data on CDs, DVDs, external hard drives or SFTP, as
`
`appropriate. The producing party shall encrypt the production data using WinRAR encryption, and
`
`the producing party shall forward the password to decrypt the production data separately from the
`
`CD, DVD, external drive or SFTP to which the production data is saved.
`
`3.
`
`Format for production of documents – hardcopy or paper documents. All
`
`documents that are hardcopy or paper files shall be scanned and produced in the same manner as
`
`documents existing in electronic format, above.
`
`4.
`
`Source code. This Stipulation does not govern the format for production of source
`
`code, which shall be produced pursuant to the relevant provision of the Protective Order.
`
`5.
`
`Parent and child emails. The parties shall produce email attachments sequentially
`
`after the parent email.
`
`6.
`
`Native files. The parties will meet and confer to discuss requests for the production
`
`of files in native format, on a case-by-case basis. If the parties are unable to reach agreement with
`
`regard to requests for additional documents in native-file format, the parties reserve the right to
`
`seek relief from the Court. Documents produced natively shall be represented in the set of imaged
`
`documents by a slipsheet indicating the production identification number and confidentiality
`
`designation for the native file that is being produced.
`
`7.
`
`Databases. Certain types of databases are dynamic in nature and will often contain
`
`information that is neither relevant nor reasonably calculated to lead to the discovery of admissible
`
`evidence. Thus, a party may opt to produce relevant and responsive information from databases
`
`3
`
`
`
`Case 1:19-cv-01245-LPS Document 30 Filed 05/01/20 Page 4 of 7 PageID #: 289
`
`
`
`in an alternate form, such as a report or data table. These reports or data tables will be produced
`
`in a static format.
`
`The parties agree to identify the specific databases, by name, that contain the relevant and
`
`responsive information that parties produce.
`
`8.
`
` Requests for hi-resolution or color documents. The parties agree to respond to
`
`reasonable and specific requests for the production of higher resolution or color images. Nothing
`
`in this Stipulation shall preclude a producing party from objecting to such requests as unreasonable
`
`in number, timing or scope, provided that a producing party shall not object if the document as
`
`originally produced is illegible or difficult to read. The producing party shall have the option of
`
`responding by producing a native-file version of the document. If a dispute arises with regard to
`
`requests for higher resolution or color images, the parties will meet and confer in good faith to try
`
`to resolve it.
`
`9.
`
`Foreign language documents. All documents shall be produced in their original
`
`language. Where a requested document exists in a foreign language and the producing party also
`
`has an English-language version of that document that it prepared for non-litigation purposes prior
`
`to filing of the lawsuit, the producing party shall produce both the original document and all
`
`English-language versions. In addition, if the producing party has a certified translation of a
`
`foreign-language document that is being produced, (whether or not the translation is prepared for
`
`purposes of litigation) the producing party shall produce both the original document and the
`
`certified translation. Nothing in this agreement shall require a producing party to prepare a
`
`translation, certified or otherwise, for foreign language documents that are produced in discovery.
`
`4
`
`
`
`Case 1:19-cv-01245-LPS Document 30 Filed 05/01/20 Page 5 of 7 PageID #: 290
`
`
`
`Dated: May 1, 2020
`
`YOUNG CONAWAY STARGATT & TAYLOR LLP
`
`POTTER ANDERSON & CORROON LLP
`
`
`
`
`
`
`
`/s/ Karen L. Pascale
`Karen L. Pascale (#2903)
`Robert M. Vrana (#5666)
`Rodney Square
`1000 North King Street
`Wilmington, DE 19801
`(302) 571-6600
`kpascale@ycst.com
`rvrana@ycst.com
`
`Counsel for Plaintiff, LBT IP I LLC
`
`
`
`
`
`
`
`/s/ David E. Moore
`David E. Moore (#3983)
`Bindu A. Palapura (#5370)
`Stephanie E. O’Byrne (#4446)
`Tracey E. Timlin (#6469)
`Hercules Plaza, 6th Floor
`1313 N. Market Street
`Wilmington, DE 19801
`(302) 984-6000
`dmoore@potteranderson.com
`bpalapura@potteranderson.com
`sobyrne@potteranderson.com
`ttimlin@potteranderson.com
`
`Counsel for Defendant, Apple Inc.
`
`
`
`SO ORDERED this _____ day of ___________, 2020.
`
`
`
`________________________________
`UNITED STATES DISTRICT JUDGE
`
`5
`
`
`
`Case 1:19-cv-01245-LPS Document 30 Filed 05/01/20 Page 6 of 7 PageID #: 291
`
`
`
`Field Name
`
`BegDoc
`
`EXHIBIT A
`TABLE OF METADATA FIELDS
`
`Field Type
`
`Specifications
`Field Name
`
`Unique ID
`(Bates number)
`
`Paragraph
`
`Description
`(Email)
`
`The Document
`ID number
`associated with
`the first page
`of an email.
`
`The Document
`ID number
`associated with
`the last page of
`an email.
`
`The Document
`ID number
`associated with
`the first page
`of a parent
`email.
`
`The Document
`ID number
`associated with
`the last page of
`the last
`attachment to a
`parent email.
`
`Description (E-
`Files/Attachments)
`
`The Document ID
`number associated
`with the first page
`of a document
`
`The Document ID
`number associated
`with the last page
`of a document.
`
`The Document ID
`number associated
`with the first page
`of a parent
`document.
`
`The Document ID
`number associated
`with the last page
`of the last
`attachment to a
`parent document.
`
`EndDoc
`
`Unique ID
`(Bates number)
`
`Paragraph
`
`BegAttach
`
`Paragraph
`
`Unique ID
`(Bates number)
`Parent-Child
`Relationships
`
`EndAttach
`
`Paragraph
`
`Unique ID
`(Bates number)
`Parent-Child
`Relationship
`
`Pages
`
`Pages
`
`Number
`
`The number of
`pages for an
`email.
`
`The number of
`pages for a
`document.
`
`DateSent
`
`
`
`Date
`(MM/DD/YYYY
`format)
`
`The date the
`email was sent.
`
`For email
`attachments, the
`date the parent
`email was sent.
`
`The name of the
`author as identified
`by the metadata of
`the document.
`
`Author
`
`Author Display
`Name (e-mail)
`
`Paragraph
`
`To
`
`Recipient
`
`Paragraph
`
`The display
`name of the
`author or
`sender of an
`email.
`
`The display
`name of the
`recipient(s) of
`an email.
`
`The display name
`of the recipient(s)
`of a document (e.g.,
`fax recipients).
`
`Exhibit A
`
`Page 1 of 2
`
`
`
`Case 1:19-cv-01245-LPS Document 30 Filed 05/01/20 Page 7 of 7 PageID #: 292
`
`EXHIBIT A
`TABLE OF METADATA FIELDS
`(. . . Continued)
`
`
`
`CC
`
`CC
`
`Paragraph
`
`BCC
`
`BCC
`
`Paragraph
`
`
`
`
`
`The display
`name of the
`copyee(s) of a
`email.
`
`The display
`name of the
`blind copyee(s)
`of an email.
`
`Subject
`
`Subject (e-mail) Paragraph
`
`Custodian
`
`Custodian
`
`Paragraph
`
`The subject
`line of an
`email.
`
`The subject of a
`document from
`entered metadata.
`
`The custodian
`of an email.
`
`The custodian of a
`document.
`
`
`
`
`
`Exhibit A
`
`Page 2 of 2
`
`