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–Xxxxx, 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. 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 Based on the foregoing, IT IS SO ORDERED. 16 DATED: 18 20 21 The Honorable 22 UNITED STATES DISTRICT JUDGE 23 26
Metadata fields. The parties are to confer and agree on whether metadata is to 13 be produced or may be excluded from discovery. Metadata may not be relevant to the issues 14 presented or, if relevant, may not be reasonably subject to discovery, or may be subject to 15 cost- shifting, considering the factors set forth in Fed. R. Civ. P. 26(b)(2)(C). For example, if 16 one party is producing only paper documents, and the other party is producing ESI, the 17 parties should confer on whether the additional cost and burden of producing metadata 18 by the party producing ESI is reasonable or should be shifted under the facts and
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: FIELD NAME DESCRIPTION EXAMPLE / FORMAT PRODBEGBATES The production Xxxxx number associated with the first page of a document. ABC0000001 PRODENDBATES The production Xxxxx number associated with last page of a document. ABC0000003 PRODBEGATTACH The production Xxxxx number associated with the first page of the parent document. ABC0000001 PRODENDATTACH The production Xxxxx 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. Xxx, Xxxx 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 Xxxxx number if the document is produced. \TEXT\ABC000001.txt
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 AGREEMENT REGARDING DISCOVERY OF ELECTRONICALLY STORED INFORMATION AND ORDER PAGE - 5 25 (Case No. 2:21-CV-00732-BJR) 1 and non-privileged: document type; custodian and duplicate custodians (or storage location if no
Metadata fields. The parties are to confer and agree on whether metadata is to 13 be produced or may be excluded from discovery. Metadata may not be relevant to the issues 14 presented or, if relevant, may not be reasonably subject to discovery, or may be subject to 15 cost- shifting, considering the factors set forth in Fed. R. Civ. P. 26(b)(2)(C). For example, if 16 one party is producing only paper documents, and the other party is producing ESI, the 17 parties should confer on whether the additional cost and burden of producing metadata 18 by the party producing ESI is reasonable or should be shifted under the facts and 19 circumstances of the case. If the parties agree to produce metadata, and unless otherwise 20 agreed, each party shall produce the following metadata associated with ESI to the extent 21 reasonably accessible: (a) the author(s) of the ESI; (b) the recipient(s) of the ESI; (c) the 22 date the ESI was created; and (d) the source from which the ESI was produced. The 23 “source” of ESI shall be the name of the person who was the custodian of the ESI or, if 24 the name of a person is not available, the storage location (e.g., “Regulatory Shared 00 Xxxxx–Xxxxx, PA”). This information will be included in the “Author,” “Recipient,” 26 “Date,” and “Source” fields (respectively) for each document in the load file 1 associated with the document images. Although it is presumed generally that the above 2 list of metadata fields will be provided, the list of metadata fields is intended to be flexible 3 and may be changed by agreement of the parties, particularly in light of advances and 4 changes in technology, vendor and business practices.
Metadata fields. The following metadata fields shall be provided, to the extent 15 available, for any particular produced document or electronic file: document type; custodian and 16 duplicate custodians (or storage location if no custodian); author/from; recipient/to, cc and bcc;
Metadata fields. The parties agree that ESI will be produced with the following metadata fields, to the extent they are reasonably accessible: 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 types is intended to be flexible and may be changed by agreement of the parties.
