Which field indicates whether a document has natives?

Which field indicates whether a document has natives?

• A. a yes/no field indicating whether a document has natives
• B. a numeric field counting native types
• C. a text field with native file paths
• D. a yes/no field indicating whether a document has OCR

Answer: (A)

The key idea is to track the simple presence or absence of a native version with a boolean indicator. In eDiscovery, “natives” means the original file formats (Word, Excel, etc.) as opposed to converted or scanned representations. A yes/no field that answers whether a native version exists is the clearest, quickest way to flag documents that have their native forms for review or production. Using a numeric field would add unnecessary complexity, trying to count how many native types a document has rather than simply whether any native exists. A text field with file paths provides detail but isn’t a direct, uniform indicator and can be inconsistent. A yes/no field about OCR answers a different question—whether text was extracted from images—not whether a native version is available.

The key idea is to track the simple presence or absence of a native version with a boolean indicator. In eDiscovery, “natives” means the original file formats (Word, Excel, etc.) as opposed to converted or scanned representations. A yes/no field that answers whether a native version exists is the clearest, quickest way to flag documents that have their native forms for review or production.

Using a numeric field would add unnecessary complexity, trying to count how many native types a document has rather than simply whether any native exists. A text field with file paths provides detail but isn’t a direct, uniform indicator and can be inconsistent. A yes/no field about OCR answers a different question—whether text was extracted from images—not whether a native version is available.