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. 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 that only the following metadata fields need to be produced: document type; custodian and duplicate custodians; author/from; recipient/to; cc and bcc; title/subject; file name and size; original file path; 11 date and time created, sent, modified, and/or received; and hash value. DATED this 10th day of April, 2018. 14 XXXXXXXX XXXX 15 16 By s/Xxxxx X. Xxxxxx
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. 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.
Metadata fields. The parties agree that only the following metadata fields need be 25 produced, and only to the extent it is reasonably accessible and non-privileged: document type; 26 custodian and duplicate custodians (or storage location if no custodian); author/from; recipient/to, 4 cc and bcc; title/subject; email subject; file name; file size; file extension; original file path; date 5 and time created, sent, modified and/or received; hash value; and confidentiality designation. 6 Productions shall include family information between documents, such as indicating when 7 documents are attached to an email. Parties shall identify whether each document contains hidden 8 content in Microsoft Office files as well as any comments or annotations in PDF files. The list 9 of metadata type is intended to be flexible and may be changed by agreement of the parties, 10 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 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. If the requesting party seeks metadata, the parties agree that only the following metadata fields need be produced: document type; custodian and duplicate custodians; author/from; recipient/to, cc and bcc; title/subject; file name and size; original file path; date and time created, sent, modified and/or received; and hash value. DATED: August 5, 2019 Xxxxxx Xxxxxx LLP /s/ Xxxxx Xxxxxxx Xxxxx Xxxxxxx Attorneys for Plaintiff Curevo, Inc. DATED: August 5, 2019 Xxxxx Xxxxxx Xxxxxxx /s/ Xxxx XxXxxx Xxxx XxXxxx Attorneys for Defendant Senyon Xxxxx Xxxx PURSUANT TO STIPULATION, IT IS SO ORDERED Dated this 7th day of August, 2019. A
