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 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. 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. 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 7 the following metadata fields need be produced: begin xxxxx number; end xxxxx number; begin 8 attachment xxxxx number; end attachment xxxxx number; document type; custodian; duplicate
Metadata fields. If the requesting party seeks metadata, the parties agree that only
Metadata fields. If the requesting party seeks metadata, the parties agree that 25 Appendix A will govern the production of metadata. The list of metadata type is intended to be 26 flexible and may be changed by agreement of the parties, particularly in light of advances and 27 changes in technology, vendor, and business practices, 28
Metadata fields. The parties agree that, to the extent these fields are reasonably 2 available, and are not privileged or protected by the attorney work-product doctrine, the following 3 metadata fields will accompany all ESI productions, in delimited load files (DAT). The parties 4 further agree to produce DAT files using the following delimiters:
5 a) Column Delimiter: ASCII Code 020 ¶
6 b) Quote: ASCII Code 254 þ
7 c) New Line: ASCII Code 174 ®
8 d) Multi-value delimiter: ASCII Code 059 ;
Metadata fields. The parties agree that only the following metadata fields need be 2 produced, and only to the extent it is reasonably accessible and non-privileged: document type;
