throbber
Case 1:22-cv-00252-MSG Document 111 Filed 06/12/23 Page 1 of 4 PageID #: 1580
`
`IN THE UNITED STATES DISTRICT COURT
`
`FOR THE DISTRICT OF DELAWARE
`
`ARBUTUS BIOPHARMA CORPORATION
`and GENEVANT SCIENCES GmbH,
`
`Plaintiffs,
`
`v.
`
`MODERNA, INC. and MODERNATX, INC.,
`
`Defendants.
`
`MODERNA, INC. and MODERNATX, INC.,
`
`Counterclaim-Plaintiffs,
`
`v.
`
`ARBUTUS BIOPHARMA CORPORATION
`and GENEVANT SCIENCES GmbH,
`
`Counterclaim-Defendants.
`
`)
`)
`)
`)
`)
`) C.A. No. 22-252-MSG
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`
`ORDER REGARDING DISCOVERY, INCLUDING DISCOVERY OF
`ELECTRONICALLY STORED INFORMATION (“ESI”)
`
`Plaintiffs Arbutus Biopharma Corporation (“Arbutus”) and Genevant Sciences GmbH
`
`(“Genevant”), and Defendants Moderna, Inc. and ModernaTX, Inc. (collectively, “Moderna,”
`
`collectively with Plaintiffs, the “Parties,” and each Plaintiff and each Defendant individually, a
`
`“Party”) hereby stipulate that they will adhere to the Court’s Default Standard for Discovery,
`
`Including Discovery of Electronically Stored Information (“ESI”) with the following additional
`
`protocols:
`
`1.
`
`The Parties have agreed to the following requirements for the formatting and
`
`contents of privilege logs:
`
`1
`
`

`

`Case 1:22-cv-00252-MSG Document 111 Filed 06/12/23 Page 2 of 4 PageID #: 1581
`
`(a)
`
`(b)
`
`(c)
`
`(d)
`
`(e)
`
`2.
`
`3.
`
`Each entry shall contain control numbers or other unique identifiers that shall
`persist for the same document through any revisions or updates to the log, and
`different redacted versions.
`
`Each entry corresponding to privilege redactions in a produced document shall
`identify the Bates number of the redacted document (and if reproduced with
`different Bates numbers, identify all such Bates numbers that it has been produced
`with).
`
`Each entry shall identify, if available and not privileged, the date, sender,
`recipients, custodian, type of privilege asserted, as well as a description of the
`contents of the document sufficient to evaluate the assertion of privilege and the
`type of privilege asserted.
`
`Each Party shall produce and maintain only one privilege log for withheld and
`redacted documents, with updates, revisions, and supplements causing
`reproduction of the single log in full, with new entries placed consecutively after
`pre-existing entries.
`
`Each Party shall produce a copy of the privilege log in Excel format if requested
`by the opposing Party.
`
`The Parties will meet and confer to agree on a time for service of privilege logs.
`
`With respect to information generated after the date of the complaint in this case,
`
`February 28, 2022, the Parties are not required to include any such information in privilege logs
`
`reflecting communications with and/or between inside and outside counsel.
`
`4.
`
`The Parties have stipulated to a procedure for addressing the inadvertent production
`
`of privileged or otherwise protected material in the Stipulated Protective Order (D.I. 85).
`
`5.
`
`(a)
`
`(b)
`
`Specific E-Discovery Issues.
`
`Search methodology. If the producing party elects to use search terms to locate
`potentially responsive ESI, it shall disclose the search terms to the requesting
`party. Absent a showing of good cause, a requesting party may request no more
`than 10 additional terms to be used in connection with the electronic search.
`Focused terms, rather than over-broad terms (e.g., product and company names),
`shall be employed. The parties must negotiate in good faith as to limitations to
`those search terms to avoid an unreasonable number of search hits.
`
`Format. ESI and non-ESI shall be produced to the requesting Party as text
`searchable image files (e.g., PDF or TIFF). When a text-searchable image file is
`produced, the producing Party must preserve the integrity of the underlying ESI,
`
`2
`
`

`

`Case 1:22-cv-00252-MSG Document 111 Filed 06/12/23 Page 3 of 4 PageID #: 1582
`
`i.e., the original formatting, the metadata (as noted below). The Parties shall
`produce their information in the following format: single-page TIFF images and
`associated multipage text files containing extracted text or OCR with
`Concordance and Opticon load files containing all requisite information including
`relevant metadata. If a receiving Party believes that color or high-resolution
`images are important to understand a particular document, a Party may request
`that the document be produced in color or as high-resolution images.
`
`Redactions for Non-Responsiveness. Absent agreement between the Parties, the
`Parties are not permitted to redact responsive or partially responsive documents
`for Non-Responsiveness. Nothing in this sub-paragraph prevents a Party from
`redacting privileged material, patient Personal Identifiable Information, or other
`information to comply with applicable laws.
`
`Native files. The only files that may be produced in native format are files not
`easily converted to image format, such as Excel and Access files. PowerPoint
`files shall be produced as text searchable image files (e.g., PDF or TIFF) that
`include speaker notes, if present. A Party may request native versions of any such
`files, and if the Parties are unable to agree to their production after meeting and
`conferring, the requesting Party may move the Court for their production. The
`producing Party shall bear the burden to show why such documents should not be
`re-produced in native format.
`
`De-duplication. Documents should be de-duplicated at the family-group level
`provided that the producing Party identifies the additional custodians in the
`Custodian(s) field or All Custodians field and the additional file paths in the All
`File Path(s) field.
`
`Metadata fields. Parties are only obligated to provide the following metadata for
`all ESI produced, to the extent such metadata exists and is able to be accurately
`collected (Metadata such as “Email Subject,” “File Path,” “FileName,” and
`“DocText” may be redacted for privilege):
`
`(c)
`
`(d)
`
`(e)
`
`(f)
`
`ProdBeg
`ProdEnd
`ProdBegAttach
`ProdEndAttach
`Email From
`Email To
`Email CC
`Email BCC
`Email Date Sent
`Email Time Sent
`File Size
`File Extension
`All File Path(s)
`
`Email Subject
`Conversation Index
`FileName
`Author
`DateCreated
`DateLastModified
`EmailRecDate
`EmailRecTime
`MD5HASH or SHA Hash
`DocText (File Path to document text file)
`All Custodian(s)
`Protective Order Confidentiality Designation
`
`3
`
`

`

`Case 1:22-cv-00252-MSG Document 111 Filed 06/12/23 Page 4 of 4 PageID #: 1583
`
`6.
`
`Any Party that produces documents produced to it by a third party, such as in
`
`response to a subpoena, shall produce such documents in the format in which they were produced
`
`by the third party.
`
`
`
`/s/ Nathan R. Hoeschen
`John W. Shaw (No. 3362)
`Karen E. Keller (No. 4489)
`Nathan R. Hoeschen (No. 6232)
`SHAW KELLER LLP
`I.M. Pei Building
`1105 North Market Street, 12th Floor
`Wilmington, DE 19801
`(302) 298-0700
`jshaw@shawkeller.com
`kkeller@shawkeller.com
`nhoeschen@shawkeller.com
`Attorneys for Plaintiffs
`
`Dated: June 9, 2023
`
`/s/ Travis J. Murray
`Jack B. Blumenfeld (No. 1014)
`Brian P. Egan (No. 6227)
`Travis J. Murray (No. 6882)
`MORRIS, NICHOLS, ARSHT & TUNNELL LLP
`1201 North Market Street
`P.O. Box 1347
`Wilmington, DE 19899
`(302) 658-9200
`jblumenfeld@morrisnichols.com
`began@morrisnichols.com
`tmurray@morrisnichols.com
`Attorneys for Defendants
`
`SO ORDERED this 12th day of June, 2023.
`
`_________________________________
`/s/ Mitchell S. Goldberg
` UNITED STATES DISTRICT JUDGE
`
`4
`
`

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