throbber
Case 2:20-cv-00337-JRG Document 65 Filed 03/16/21 Page 1 of 7 PageID #: 452
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`CIVIL ACTION NO. 2:20-cv-00337-JRG
`


` §
`
`
`§ §
`
`




`
`SEAGEN INC.,
`
`
`Plaintiff,
`
`v.
`
`
`
`
`
`
`
`
`
`
`
`DAIICHI SANKYO CO., LTD.,
`
`Defendant.
`
`ORDER REGARDING E-DISCOVERY
`
`The Court ORDERS as follows:
`
`1.
`
`This order supplements all other discovery rules and orders. It streamlines Electronically
`
`Stored Information (“ESI”) production to promote a “just, speedy, and inexpensive
`
`determination” of this action, as required by Federal Rule of Civil Procedure 1.
`
`This order may be modified in the Court’s discretion or by agreement of the Parties.
`
`A Party’s meaningful compliance with this order and efforts to promote efficiency and
`
`2.
`
`3.
`
`reduce costs will be considered in cost-shifting determinations.
`
`4.
`
`Absent a showing of good cause, general ESI production requests under Federal Rules of
`
`Civil Procedure 34 and 45, or compliance with a mandatory disclosure requirement of this
`
`Court, shall not include metadata. However, fields showing the date and time that the
`
`document was sent and received, as well as the complete distribution list, shall generally
`
`be included in the production if such fields exist.
`
`5.
`
`Absent agreement of the Parties or further order of this Court, the following parameters
`
`shall apply to ESI production:
`
`

`

`Case 2:20-cv-00337-JRG Document 65 Filed 03/16/21 Page 2 of 7 PageID #: 453
`
`A.
`
`General Document Image Format. Each electronic document shall be produced
`
`in the form in which it is ordinarily maintained (“native format”) or in single-page
`
`Tagged Image File Format (“TIFF”) format. Files produced in native format shall
`
`have a TIFF Image indicating that the file was produced natively and having a
`
`metadata field that identifies the file path for the location of the associated native
`
`file within the production load file. TIFF files shall be single page and shall be
`
`named with a unique production number followed by the appropriate file extension.
`
`Load files shall be provided to indicate the location and unitization of the TIFF
`
`files. If a document is more than one page, the unitization of the document and any
`
`attachments and/or affixed notes shall be maintained as they existed in the original
`
`document.
`
`B.
`
`Text-Searchable Documents. No Party has an obligation to make its production
`
`text-searchable; however, if a Party’s documents already exist in text-searchable
`
`format independent of this litigation, or are converted to text-searchable format
`
`for use in this litigation, including for use by the producing Party’s counsel, then
`
`such documents shall be produced in the same text-searchable format at no cost to
`
`the receiving Party.
`
`C.
`
`Footer. Each document image shall contain a footer with a sequentially ascending
`
`production number.
`
`D.
`
`Native Files. A Party that receives a document produced in a format specified
`
`above may make a reasonable request to receive the document in its native format,
`
`and upon receipt of such a request, the producing Party shall produce the document
`
`in its native format.
`
`- 2 -
`
`

`

`Case 2:20-cv-00337-JRG Document 65 Filed 03/16/21 Page 3 of 7 PageID #: 454
`
`E.
`
`Databases. The Parties agree to undertake reasonable efforts to provide data from
`
`databases or other structured data sources in a reasonably useful format consistent
`
`with how such data is stored in the ordinary course of business.
`
`F.
`
`No Backup Restoration Required. Absent a showing of good cause, no Party
`
`need restore any form of media upon which backup data is maintained in a Party’s
`
`normal or allowed processes, including but not limited to backup tapes, disks,
`
`SAN, and other forms of media, to comply with its discovery obligations in the
`
`present case. Absent a showing of good cause, the following categories of ESI
`
`are deemed not reasonably accessible and need not be collected and preserved:
`
`i.
`
`ii.
`
`Deleted, “slack,” fragmented, or unallocated data;
`
`Random access memory (RAM), temporary files, or other
`
`ephemeral data that are difficult to preserve without disabling the
`
`operating system;
`
`iii.
`
`Online access data such as (without limitation) temporary internet
`
`files, history files, cache files, and cookies; and
`
`iv.
`
`Server, system, network, or software application logs.
`
`G.
`
`Voicemail and Mobile Devices. Absent a showing of good cause, voicemails,
`
`PDAs and mobile phones are deemed not reasonably accessible and need not be
`
`collected and preserved.
`
`6.
`
`General ESI production requests under Federal Rules of Civil Procedure 34 and 45, or
`
`compliance with a mandatory disclosure order of this Court, shall not include e-mail or
`
`other forms of electronic correspondence (collectively “e-mail”). To obtain e-mail,
`
`Parties must propound specific e-mail production requests.
`
`- 3 -
`
`

`

`Case 2:20-cv-00337-JRG Document 65 Filed 03/16/21 Page 4 of 7 PageID #: 455
`
`7.
`
`E-mail production requests shall be phased to occur timely after the Parties have exchanged
`
`initial disclosures, a specific listing of likely e-mail custodians, a specific identification of
`
`the fifteen most significant listed e-mail custodians in view of the pleaded claims and
`
`defenses,1 infringement contentions and accompanying documents pursuant to P.R. 3-1
`
`and 3-2, invalidity contentions and accompanying documents pursuant to P.R. 3-3 and 3-
`
`4, and preliminary information relevant to damages. The exchange of this information
`
`shall occur at the time required under the Federal Rules of Civil Procedure, Local Rules, or
`
`by order of the Court. Each requesting Party may also propound up to five written
`
`discovery requests and take one deposition per producing Party to identify the proper
`
`custodians, proper search terms, and proper time frame for e-mail production requests.
`
`The Court may allow additional discovery upon a showing of good cause.
`
`8.
`
`E-mail production requests shall identify the custodian, search terms, and time frame. The
`
`Parties shall cooperate to identify the proper custodians, proper search terms, and proper
`
`time frame. For avoidance of doubt, e-mail production requests to custodians shall be
`
`limited to only e-mail or other forms of electronic correspondence. Each requesting Party
`
`shall limit its e-mail production requests to a total of eight custodians per producing Party
`
`for all such requests. The Parties may jointly agree to modify this limit without the
`
`Court’s leave. The Court shall consider contested requests for additional or fewer
`
`custodians per producing Party, upon showing a distinct need based on the size,
`
`complexity, and issues of this specific case.
`
`9.
`
`Each requesting Party shall limit its e-mail production requests to a total of ten search terms
`
`1 A “specific identification” requires a short description of why the custodian is believed to be
`significant.
`
`- 4 -
`
`

`

`Case 2:20-cv-00337-JRG Document 65 Filed 03/16/21 Page 5 of 7 PageID #: 456
`
`per custodian per Party. The Parties may jointly agree to modify this limit without the
`
`Court’s leave. The Court shall consider contested requests for additional or fewer search
`
`terms per custodian, upon showing a distinct need based on the size, complexity, and
`
`issues of this specific case. The search terms shall be narrowly tailored to particular
`
`issues. Indiscriminate terms, such as the producing company’s name or its product name,
`
`are inappropriate unless combined with narrowing search criteria that sufficiently reduce
`
`the risk of overproduction. A conjunctive combination of multiple words or phrases (e.g.,
`
`“computer” and “system”) narrows the search and shall count as a single search term. A
`
`disjunctive combination of multiple words or phrases (e.g., “computer” or “system”)
`
`broadens the search, and thus each word or phrase shall count as a separate search term
`
`unless they are variants of the same word. Use of narrowing search criteria (e.g., “and,”
`
`“but not,” “w/x”) is encouraged to limit the production and shall be considered when
`
`determining whether to shift costs for disproportionate discovery. If any search term, date
`
`range, or custodian results in overly broad results, the Parties will meet and confer in good
`
`faith to consider refining or modifying the search terms, date range, or custodian.
`
`10.
`
`E-mails from Non-Custodians. To the extent that a Party elects to make a voluntary
`
`production of an e-mail from an individual that is not designated as an e-mail custodian,
`
`the Parties shall meet and confer regarding requests for any additional e-mails from such
`
`individual. The Court shall consider contested requests for any additional e-mails from
`
`non-custodians, upon showing a distinct need based on the voluntarily produced e-mail
`
`and the specific issues of this case.
`
`11.
`
`To contain costs in the identification of non-duplicative relevant ESI from the email
`
`collections of identified custodians for review and production, the Parties may use
`
`- 5 -
`
`

`

`Case 2:20-cv-00337-JRG Document 65 Filed 03/16/21 Page 6 of 7 PageID #: 457
`
`advanced search and retrieval technologies, including e mail threading, predictive coding,
`
`or other technology-assisted review, given the use of such technology is disclosed to the
`
`other Party prior to its use. In the case of a Party’s disclosure of the intended use of
`
`predictive coding or technology assisted review, within seven days of disclosure, the other
`
`Party is permitted to request information regarding the confidence metrics to be used. The
`
`Parties agree to meet and confer regarding the specific analytics and confidence metrics
`
`that will be exchanged and a schedule for the exchange.
`
`12.
`
`The Parties will take reasonable steps, prior to production, to unencrypt and restore any
`
`discoverable ESI that is encrypted (e.g., password-protected) and will produce relevant,
`
`non-privileged, responsive documents that can be reasonably unencrypted and restored.
`
`13.
`
`Pursuant to Federal Rule of Evidence 502(d) and Paragraph 12 of the Protective Order
`
`(Dkt. No. 55), both of which are expressly incorporated herein, the inadvertent production
`
`of a privileged or work product protected ESI is not a waiver in the pending case or in any
`
`other federal or state proceeding.
`
`14.
`
`The Producing Party may redact from any TIFF image, metadata field, or native file
`
`material that is protected from disclosure by applicable privilege or immunity, that is
`
`governed by either domestic or foreign privacy laws or regulations, private personal
`
`information of employees or other persons, or other information that the Protective Order
`
`allows to be redacted.
`
`15.
`
`The mere production of ESI in a litigation as part of a mass production shall not itself
`
`constitute a waiver for any purpose.
`
`16.
`
`Except as expressly stated, nothing in this order affects the Parties’ discovery obligations
`
`under the Federal or Local Rules.
`
`- 6 -
`
`

`

`Case 2:20-cv-00337-JRG Document 65 Filed 03/16/21 Page 7 of 7 PageID #: 458
`
`- 7 -
`
`.
`
`____________________________________
`RODNEY GILSTRAP
`UNITED STATES DISTRICT JUDGE
`
`So ORDERED and SIGNED this 16th day of March, 2021.
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket