eDiscovery Rulings: Metadata and Hyperlinked Files Explained

Introduction to Recent eDiscovery Decisions

Two notable 2024 eDiscovery decisions — Moore v. Garnand and In re Uber Technologies, Inc. Passenger Sexual Assault Litigation — shed light on evolving judicial expectations around electronically stored information (ESI), metadata, and the treatment of hyperlinked files in modern litigation.

The Importance of Metadata in eDiscovery

Metadata plays a critical role in eDiscovery by providing context for digital documents — revealing when files were created, modified, or shared, and by whom. Courts have increasingly recognized that metadata is not a peripheral detail but an intrinsic component of ESI that can be essential to establishing the timeline and authenticity of digital evidence.

Moore v. Garnand: Case Analysis

Moore v. Garnand, WL 3291810 (D. Arizona 2024), centered on a party's failure to produce relevant metadata in response to discovery requests. The plaintiffs argued that metadata associated with electronically stored information was necessary for understanding the context and timeline of the case. The defendants resisted full compliance, contending that metadata was not essential and that its production was unduly burdensome.

The court granted the plaintiffs' motion to compel, rejecting both of the defendants' arguments. The ruling held that metadata is an intrinsic part of ESI and must be produced when requested unless there is strong justification for withholding it. The court determined that metadata is necessary to provide a complete and accurate representation of digital evidence, helping to establish when and how documents were created, modified, or shared.

The plaintiffs had sought sanctions under Rule 37(b), which applies to violations of court orders. However, the court clarified that Rule 37(c) was the proper provision in this context, as it addresses failures to provide ESI as part of initial disclosures required under Rule 26. Because there was no prior court order requiring production of metadata, Rule 37(b) was inapplicable. The defendants' failure to produce metadata was therefore deemed a violation of Rule 37(c), which authorizes sanctions when a party does not comply with its discovery obligations.

The key takeaway from this case is that litigants must be mindful of their obligations under Rule 26 to avoid penalties under Rule 37(c).

ESI Protocol Disputes and Hyperlinked Files

In re Uber Technologies, Inc. Passenger Sexual Assault Litigation, 2024 WL 1772832 (N.D. Cal. 2024), involved a dispute over Uber's ESI protocol concerning hyperlinked files embedded within emails and chat messages. Uber utilized Google Workspace, which allows users to include hyperlinks to Google Drive documents rather than traditional email attachments. The issue arose because hyperlinked files evolve over time, and Uber's standard eDiscovery tools did not automatically capture contemporaneous versions of those documents.

Pretrial Order No. 9 addressed the ongoing disputes regarding Uber's production of hyperlinked files and metadata, resolving key issues about how ESI should be handled. The first major issue was whether Uber was required to collect and produce contemporaneous versions of hyperlinked documents. The court ruled that Uber was not obligated to develop new technology or undertake significant automated efforts to capture those versions. However, Uber was required to manually retrieve up to 200 hyperlinked files that plaintiffs specifically identified as critical. This ruling illustrated the limitations of existing eDiscovery tools in handling cloud-based storage and the challenges of linking evolving cloud documents to the messages in which they were originally referenced.

The second major dispute concerned which metadata fields Uber was required to provide for hyperlinked files. The court ordered Uber to preserve and produce all metadata related to cloud-stored documents, including Google Vault exports. Plaintiffs also requested additional metadata fields — such as "Missing Google Drive Attachments" and "Non-Contemporaneous" — which the court granted. These fields would help identify missing hyperlinked documents and distinguish between contemporaneous and later versions, reinforcing the importance of metadata transparency in eDiscovery.

The final issue involved defining the term "attachment" for purposes of this litigation. Plaintiffs argued for a broad definition that included hyperlinked and embedded documents, while Uber sought to exclude hyperlinked documents, asserting they were distinct from traditional attachments. The court largely sided with the plaintiffs but clarified that Uber was not required to produce contemporaneous versions of hyperlinked files unless existing technology made retrieval feasible. This decision underscores the evolving challenges in eDiscovery as courts adapt to new methods of digital communication and document storage.