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;
Appears in 4 contracts
Samples: Model Agreement, cases.justia.com, formfiles.justia.com
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 15 the following metadata fields need be produced, and only to the extent it is reasonably accessible 3 16 and non-privileged: document type; custodian and duplicate custodians (or storage location if no 4 17 custodian); author/from; recipient/to, cc and bcc; title/subject; email subject; file name; file size;; 18 file extension; original file path; date and time created, sent, modified and/or received; and hash
Appears in 2 contracts
Samples: www.wawd.uscourts.gov, cases.justia.com
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)3 custodians; author/from; recipient/to, cc and bcc; title/subject; email subjectfile name and size; original file name4 path; file size;date and time created, sent, modified and/or received; and hash value. 5
Appears in 1 contract
Samples: cases.justia.com
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)custodians; 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; time zone; redacted; confidentiality; and hash
Appears in 1 contract
Samples: cases.justia.com
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 8 the following metadata fields need be produced, and only to the extent it is reasonably accessible 3 9 and non-privileged: document type; custodian and duplicate custodians (or storage location if no 4 10 custodian); author/from; recipient/to, cc and bcc; title/subject; email subject; file name; file size;
Appears in 1 contract
Samples: cases.justia.com
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 20 the following metadata fields need be produced, and only to the extent it is reasonably accessible 3 22 and non-privileged: document type; custodian and duplicate custodians (or storage location if no 4 23 custodian); author/from; recipient/to, cc and bcc; title/subject; email subject; file name; file size;
Appears in 1 contract
Samples: breakend.github.io
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 the 12 following metadata fields need be produced, and only to the extent it is reasonably accessible 3 and 13 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;no
Appears in 1 contract
Samples: cases.justia.com
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 10 the following metadata fields need be produced, and only to the extent it is reasonably accessible 3 11 and non-privileged: document type; custodian and duplicate custodians (or storage location if no 4 12 custodian); author/from; recipient/to, cc and bcc; title/subject; email subject; file name; file size;
Appears in 1 contract
Samples: 25 Agreement
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 15 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;no
Appears in 1 contract
Samples: cases.justia.com
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 20 the following metadata fields need be produced, and only to the extent it is reasonably accessible 3 21 and non-privileged: document type; custodian and duplicate custodians custodians; (or storage location if no 4 custodian); author/from; recipient/to, cc and bcc; title/subject; email subject; file name; file size;no
Appears in 1 contract
Samples: cases.justia.com
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 19 the following metadata fields need be produced, and only to the extent it is reasonably accessible 3 20 and non-privileged: document type; custodian and duplicate custodians (or storage location if no 4 21 custodian); author/from; recipient/to, cc and bcc; title/subject; email subject; file name; file size;
Appears in 1 contract
Samples: cases.justia.com
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 21 the following metadata fields need be produced, and only to the extent it is reasonably accessible 3 22 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;no
Appears in 1 contract
Samples: cases.justia.com
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 25 the following metadata fields need be produced, and only to the extent it is reasonably accessible 3 26 and non-privileged: document type; custodian and duplicate custodians (or storage location if no 4 1 custodian); author/from; recipient/to, cc and bcc; title/subject; email subject; file name; file size;
Appears in 1 contract
Samples: cases.justia.com
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 13 the following metadata fields need be produced, and only to the extent it is reasonably accessible 3 14 and non-privileged: document type; custodian and duplicate custodians (or storage location if no 4 15 custodian); author/from; recipient/to, cc and bcc; title/subject; email subject; file name; file size;
Appears in 1 contract
Samples: cases.justia.com
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 4 the following metadata fields need be produced, and only to the extent it is reasonably accessible 3 5 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;no
Appears in 1 contract
Samples: cases.justia.com
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 10 the following metadata fields need be produced, and only to the extent it is reasonably accessible 3 11 and non-privileged: document type; custodian and duplicate custodians (or storage location if no 4 12 custodian); author/from; recipient/to, cc and bcc; title/subject; email subject; file name; file size;; value. The list of metadata type is intended to be flexible and may be changed by agreement of the parties.
Appears in 1 contract
Samples: cases.justia.com
Metadata fields. If the requesting party seeks metadata, the parties agree that only 2 23 the following metadata fields need be produced, and only to the extent it is reasonably accessible 3 1 and non-privileged: document type; custodian and duplicate custodians (or storage location if no 4 2 custodian); author/from; recipient/to, cc and bcc; title/subject; email subject; file name; file size;
Appears in 1 contract
Samples: cases.justia.com