Common use of De-duplication Clause in Contracts

De-duplication. The parties may de-duplicate their ESI production across custodial 15 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 information removed during the de-duplication process tracked in a duplicate/other custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 7 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 8 information removed during the de-duplication process tracked in a duplicate/other custodian 17 9 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 information removed during the de-duplication process tracked in a duplicate/other custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 16 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 17 information removed during the de-duplication process tracked in a duplicate/other custodian 17 18 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 2 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 3 information removed during the de-duplication process tracked in a duplicate/other custodian 17 4 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 20 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 21 information removed during the de-duplication process must be tracked in a duplicate/other 22 custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across 11 custodial 15 and non-custodial data sources after disclosure to the requesting party, and the 12 duplicate custodian 16 information removed during the de-duplication process tracked in a 13 duplicate/other custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 7 and non-custodial data sources after disclosure to the requesting party. For each produced 8 document, and the metadata memorializing duplicate custodian 16 information removed during the de-de- 9 duplication process tracked shall be provided in a duplicate/other custodian 17 field in the database load file.

De-duplication. The parties may shall de-duplicate their ESI production across 18 custodial 15 and non-custodial data sources after disclosure to the requesting partysources, and the duplicate custodian 16 information removed during 19 the de-duplication process tracked in a duplicate/other custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 2 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 3 information removed during the de-duplication process tracked in a duplicate/other custodian 17 field in 4 the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 information removed during the de-duplication process tracked in a duplicate/other custodian 17 field in the database load file. De-duplication must occur by an industry standard method, including MD5 or SHA-1 Hash Values. De- duplication may not occur by manual review.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 13 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 14 information removed during the de-duplication process tracked in a duplicate/other custodian 17 15 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across 5 custodial 15 and non-custodial data sources after disclosure to the requesting party, and the 6 duplicate custodian 16 information removed during the de-duplication process tracked in a 7 duplicate/other custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across 17 custodial 15 and non-custodial data sources after disclosure to the requesting party, and the 18 duplicate custodian 16 information removed during the de-duplication process tracked in a 19 duplicate/other custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across 17 custodial 15 and non-custodial data sources after disclosure to the requesting party, and the duplicate 18 custodian 16 information removed during the de-duplication process tracked in a duplicate/other 19 custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 22 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 23 25 AGREEMENT REGARDING DISCOVERY OF ELECTRONICALLY STORED INFORMATION AND [PROPOSED] ORDER PAGE - 5 26 (Case No. C24-0319-JLR) 1 information removed during the de-duplication process tracked in a duplicate/other custodian 17 2 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 27 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 28 XXXXX XXXXXXX XXXXXXXX & XXXXXXXX LLP 1 information removed during the de-duplication process tracked in a duplicate/other custodian 17 field 2 in the database load file.

De-duplication. The parties may de-duplicate their ESI production within a given 12 custodian or globally (ie, across all custodial 15 and non-custodial data sources sources) after disclosure to 13 the requesting party, and provided that the duplicate custodian 16 information removed during the de-de- 14 duplication process is tracked in a duplicate/other custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across 22 custodial 15 and non-custodial data sources after disclosure to the requesting party, and 23 the duplicate custodian 16 information removed during the de-duplication process tracked 24 in a duplicate/other custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across 20 custodial 15 and non-custodial data sources after disclosure to the requesting party, and the 21 duplicate custodian 16 information removed during the de-duplication process tracked in a 22 duplicate/other custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 information removed during the de-duplication process tracked in a duplicate/other custodian field 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production production, using industry 11 standard MD5 or similar technology, across custodial 15 and non-custodial data sources after 12 disclosure to the requesting party, and provided that the duplicate custodian 16 information removed 13 during the de-duplication process is tracked in a duplicate/other custodian 17 field in the database 14 load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 19 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 20 information removed during the de-duplication process tracked in a duplicate/other custodian 17 21 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 information removed during the de-duplication process tracked in a duplicate/other 15 custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 21 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 22 information removed during the de-duplication process tracked in a duplicate/other custodian 17 field 23 in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 10 and non-custodial data sources after disclosure to the requesting party, and the duplicate custodian 16 11 information removed during the de-duplication process tracked in a duplicate/other custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across 7 custodial 15 and non-custodial data sources after disclosure to the requesting party, and the . The duplicate custodian 16 information removed during the de-duplication process must be tracked in a duplicate/other custodian 17 field in the database load file.

De-duplication. The parties may de-duplicate their ESI production across custodial 15 2 and non-custodial data sources after disclosure to the requesting partysources, and the duplicate custodian 16 information removed during the de-de- 3 duplication process tracked in a duplicate/other custodian 17 field in the database load file.