e-Discovery: How mandatory are the data fields requested by the Congress?
<p>Some data requests sent by the US Congress sound like they require some metadata fields to be populated attached to files, “unmodified”.</p>
<p>For example, <a href="https://www.politico.com/f/?id=0000016d-08f8-d6ab-a97f-4afb19f90000" rel="nofollow noreferrer">this request</a> (as do other similar ones) says:</p>
<blockquote>
<h4>Responding to Oversight Committee Document Requests</h4>
<ol start="5">
<li><p>Documents produced in electronic format should be organized, identified, and indexed electronically.</p>
</li>
<li><p>Electronic document productions should be prepared according to the following standards:</p>
<p>d. All electronic documents produced to the Committee should include the following fields of metadata specific to each document, and no modifications should be made to the original metadata:</p>
<p>BEGDOC, ENDDOC, TEXT, BEGATTACH, ENDATTACH, PAGECOUNT, CUSTODIAN, RECORDTYPE, DATE, TIME, SENTDATE, SENTTIME, BEGINDATE, BEGINTIME, ENDDATE, ENDTIME, AUTHOR, FROM, CC, TO, BCC, SUBJECT, TITLE, FILENAME, FILEEXT, FILESIZE, DATECREATED, TIMECREATED, DATELASTMOD, TIMELASTMOD, INTMSGID, INTMSGHEADER, NATIVELINK, INTFILPATH, EXCEPTION, BEGATTACH.</p>
</li>
</ol>
</blockquote>
<p>Assuming this is sent to a small company, it is quite possible the documents are stored on employees’ work (or even personal) computers, possibly as just Word documents. It is unlikely that they are organized in a database that would contain these fields.</p>
<p>These fields seem to be <a href="https://www.meridiandiscovery.com/articles/fields-you-should-have-in-your-e-discovery-database/" rel="nofollow noreferrer">mentioned by a discovery service provider company</a>, but I have not been quickly able to understand where these fields come from, or why Congress seems to have an expectation that the respondent will have the documents organized with these fields.</p>
<p>I’m neither a legal professional or from the US, so out of personal curiosity (and professional curiosity in the field of IT), I am trying to understand:</p>
<ul>
<li><h6>Is there is <em>an actual standard</em> that proscribes these fields?</h6>
</li>
<li><h6>Is there <em>an actual federal US legal requirement</em> to either maintain documents with this metadata (or at least generate it on export)?</h6>
</li>
<li><h6>If this applies only to businesses of certain size, what is the threshold?</h6>
</li>
</ul>
<p>That is: do I need to worry about storing small business or large corporation’s documents centrally and annotated with these fields?</p>

<p>The reasonable implication and interpretation of this is that metadata on a file to which a field is not applicable is not required.</p>
<p>For example, &quot;FROM, CC, TO, BCC&quot; while applicable to email, would not be applicable to a spreadsheet that was never shared with anyone for purposes of making a calculation. Unmodified metadata can only be provided to the extent it exists.</p>

<p>These come from an <a href="https://legal.thomsonreuters.com/en/insights/articles/what-is-esi-discovery-and-protocol-" rel="nofollow noreferrer">ESI discovery protocol</a>, which as they say</p>
<blockquote>
<p>is a mutually agreed upon plan on how both sides will access data and,
eventually, make it available to the other side</p>
</blockquote>
<p>though there is probably no mutuality in the case of Congressional discovery. It's unclear whether there is a single authoritative standard, but <a href="https://www.mdd.uscourts.gov/sites/mdd/files/ESI-Principles.pdf" rel="nofollow noreferrer">here</a> is an example (in appendix 2.1). The field &quot;INTMSGID&quot; is not defined there, so you would probably have to hire a lawyer to find out what they want. The list you cited frequently pops up in letters from Congress to federal agencies, and may be mandated in some federal record-keeping regulation. If Congress subpoenas you and your documents, they may be less presumptive and demanding.</p>

united-states discovery