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 3 custodial and non-custodial data sources after disclosure to the requesting party.
De-duplication. Removal of duplicate documents shall only be done on exact duplicate documents (based on MD5 or SHA- 1 hash values at the document level). De-duplication will be performed globally across data sets.
De-duplication. The parties may de-duplicate their ESI production across custodial 14 and non-custodial data sources after disclosure to the requesting party so long as the duplicate 15 custodian information removed during the de-duplication process is tracked in a duplicate/other 16 custodian field in the database load file. De-duplication will be based on the MD5 or SHA-1 Hash 17 values of native versions of documents. Only entire families that are exact duplicates will be 18 subjected to deduplication (i.e. if two exact duplicates are attached to two non-duplicate parent 19 emails, both families will be produced).
De-duplication. The parties shall de-duplicate their ESI production as outlined in 21 Appendix A. However, a Producing Party must still ensure that all deduplicated custodians are 22 identified in the All Custodians field, and the location of duplicate file paths are provided in the
