Metadata fields Clause Samples
The 'Metadata fields' clause defines the specific data attributes or categories that must be included with a document, record, or dataset. In practice, this clause outlines which pieces of information—such as author, creation date, version number, or classification—should be attached to each item for identification and management purposes. By standardizing the required metadata, the clause ensures consistency, facilitates efficient organization and retrieval, and reduces the risk of misclassification or loss of important information.
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 the following metadata fields need be produced, and only to the extent it is reasonably accessible 3 and non-privileged: document type; custodian and duplicate custodians (or storage location if no 4 custodian); author/from; recipient/to, cc and bcc; title/subject; email subject; file name; file size;
Metadata fields. The parties are to confer and agree on whether metadata is to be produced or may be excluded from discovery. Metadata may not be relevant to the issues presented or, if relevant, may not be reasonably subject to discovery, or may be subject to cost- shifting, considering the factors set forth in Fed. R. Civ. P. 26(b)(2)(C). For example, if one party is producing only paper documents, and the other party is producing ESI, the parties should confer on whether the additional cost and burden of producing metadata by the party producing ESI is reasonable or should be shifted under the facts and circumstances of the case. If the parties agree to produce metadata, and unless otherwise agreed, each party shall produce the following metadata associated with ESI to the extent reasonably accessible: (a) the author(s) of the ESI; (b) the recipient(s) of the ESI; (c) the date the ESI was created; and (d) the source from which the ESI was produced. The “source” of ESI shall be the name of the person who was the custodian of the ESI or, if the name of a person is not available, the storage location (e.g., “Regulatory Shared Drive–▇▇▇▇▇, PA”). This information will be included in the “Author,” “Recipient,” “Date,” and “Source” fields (respectively) for each document in the load file associated with the document images. Although it is presumed generally that the above list of metadata fields will be provided, the list of metadata fields is intended to be flexible and may be changed by agreement of the parties, particularly in light of advances and changes in technology, vendor and business practices.
Metadata fields. The parties are to confer and agree on whether metadata is to be 21 produced or may be excluded from discovery. Metadata may not be relevant to the issues 22 presented or, if relevant, may not be reasonably subject to discovery, or may be subject to cost- 23 shifting, considering the factors set forth in Fed. R. Civ. P. 26(b)(2)(C). For example, if one party 24 is producing only paper documents, and the other party is producing ESI, the parties should 25 confer on whether the additional cost and burden of producing metadata by the party 26 producing ESI is reasonable or should be shifted under the facts and circumstances of the case.
Metadata fields. If the requesting party seeks metadata, the parties agree
Metadata fields. If the requesting party seeks metadata, the parties agree that only 7 the following metadata fields need be produced: begin ▇▇▇▇▇ number; end ▇▇▇▇▇ number; begin 8 attachment ▇▇▇▇▇ number; end attachment ▇▇▇▇▇ number; document type; custodian; duplicate
Metadata fields. If the requesting party seeks metadata, the parties agree that only the following metadata fields need be produced, and only to the extent it is reasonably accessible and non-privileged: document type; custodian and duplicate custodians (or storage location if no custodian); author/from; recipient/to, cc and bcc; title/subject; email subject; file name; file size; file extension; original file path; date and time created, sent, modified and/or received; and hash value. The list of metadata type is intended to be flexible and may be changed by agreement of the parties, particularly in light of advances and changes in technology, vendor, and business practices.
Metadata fields. If the requesting party seeks metadata, the parties agree that only 23 the following metadata fields need be produced, and only to the extent it is reasonably accessible 24
Metadata fields. If the requesting party seeks metadata, the parties agree that 5 only the following metadata fields need be produced: document type; custodian and duplicate 6 custodians; author/from; recipient/to, cc and bcc; title/subject; file name and size; original file 7 path; date and time created, sent, modified and/or received; and hash value. 8 9 DATED: 10 PARTY 1 PARTY 2 By By 13 ORDER 14 Based on the foregoing, IT IS SO ORDERED. 16 DATED: 18 20 21 The Honorable 22 UNITED STATES DISTRICT JUDGE 23 26
Metadata fields. If the requesting party seeks metadata, the parties agree that 25 only the following metadata fields need be produced, and only to the extent it is reasonably 26 accessible and non-privileged: document type; custodian and duplicate custodians (or storage 1 location if no custodian); author/from; recipient/to, cc and bcc; title/subject; email subject; file 3 received; and hash value. The list of metadata type is intended to be flexible and may be 4 changed by agreement of the parties, particularly in light of advances and changes in 5 technology, vendor, and business practices.
Metadata fields. The following information shall be produced for hard copy documents and provided in the data load file at the same time that the TIFF images and the Optical Character Recognition (OCR)-acquired text files are produced. Each metadata field shall be labeled as listed below: PRODBEGBATES The production ▇▇▇▇▇ number associated with the first page of a document. ABC0000001 PRODENDBATES The production ▇▇▇▇▇ number associated with last page of a document. ABC0000003 PRODBEGATTACH The production ▇▇▇▇▇ number associated with the first page of the parent document. ABC0000001 PRODENDATTACH The production ▇▇▇▇▇ number associated with the last page of the last attachment in the document family. ABC0000008 PGCOUNT Total number of pages for a document. 00006 CUSTODIAN The name of the primary person the files belong to. This field should be populated as last name, first name. ▇▇▇, ▇▇▇▇ PRODVOLID Production volume name. ABC_PROD001 TEXTLINK The path to the full extracted OR OCR text of the document. Text files should be named per control number or ▇▇▇▇▇ number if the document is produced. \TEXT\ABC000001.txt