Relativity Processing Specialist
- Processing Profile –
Deduplication with 100%
correct answers
What is deduplication?
The method for separating duplicate files during discovery. During
deduplication, the system compares documents based on certain
characteristics and keeps just one instance of an item when two or
more copies exist. The system performs deduplication against
published files only. Deduplication doesn't occur during inventory or
discovery. Deduplication only applies to parent files; it doesn't apply
to children. If a parent is published, all of its children are also
published
Deduplication method - why should you not change the
deduplication method when running a set?
Doing so could result in blank DeDuped Custodians or DeDuped
paths fields after publish, when those fields would otherwise display
deduplication information
Previous
Play
Next
Rewind 10 seconds
Move forward 10 seconds
Unmute
0:00
/
0:15
Full screen
, Brainpower
Read More
Deduplication - None
No deduplication occurs. Even when you select None as the
deduplication method, Relativity identifies duplicates by storing one
copy of the native document on the file repository and using
metadata markers for all duplicates of that document. .Relativity
doesn't repopulate duplicate documents if you change the
deduplication method from None after processing is
complete. Changing the deduplication method only affects
subsequent processing sets. This means that if you select global
deduplication for your processing settings, you can't then tell
Relativity to include all duplicates when you go to run a production
Deduplication - Global
Arranges for documents from each processing data source to be de-
duplicated against all documents in all other data sources in your
workspace. Selecting this makes the Propagate deduplication data
field below visible and required. If you select Global, there should
be no exact e-mail duplicates in the workspace after you publish.
The only exception is a scenario in which two different e-mail
systems are involved, and the e-mails are different enough that the
processing engine can't exactly match them. In the rare case that
this happens, you may see email duplicates in the workspace.
Deduplication - Custodial
Arranges for documents from each processing data source to be de-
duplicated against only documents in data sources owned by that
custodian. Selecting this makes the Propagate deduplication data
field below visible and required. Deduplication is run on custodian
ID's; there's no consequence to changing a custodian's name after
their files have already been published.
Propagate Deduplication Data - What does this mean?
Applies the deduplication fields you mapped out of deduped
custodians, deduped paths, all custodians, and all paths field data
to children documents, which allows you to meet production
specifications and perform searches on those fields without having
to include family or overlay those fields manually. This field is only
available if you selected Global or Custodial for the deduplication
method above.
- Processing Profile –
Deduplication with 100%
correct answers
What is deduplication?
The method for separating duplicate files during discovery. During
deduplication, the system compares documents based on certain
characteristics and keeps just one instance of an item when two or
more copies exist. The system performs deduplication against
published files only. Deduplication doesn't occur during inventory or
discovery. Deduplication only applies to parent files; it doesn't apply
to children. If a parent is published, all of its children are also
published
Deduplication method - why should you not change the
deduplication method when running a set?
Doing so could result in blank DeDuped Custodians or DeDuped
paths fields after publish, when those fields would otherwise display
deduplication information
Previous
Play
Next
Rewind 10 seconds
Move forward 10 seconds
Unmute
0:00
/
0:15
Full screen
, Brainpower
Read More
Deduplication - None
No deduplication occurs. Even when you select None as the
deduplication method, Relativity identifies duplicates by storing one
copy of the native document on the file repository and using
metadata markers for all duplicates of that document. .Relativity
doesn't repopulate duplicate documents if you change the
deduplication method from None after processing is
complete. Changing the deduplication method only affects
subsequent processing sets. This means that if you select global
deduplication for your processing settings, you can't then tell
Relativity to include all duplicates when you go to run a production
Deduplication - Global
Arranges for documents from each processing data source to be de-
duplicated against all documents in all other data sources in your
workspace. Selecting this makes the Propagate deduplication data
field below visible and required. If you select Global, there should
be no exact e-mail duplicates in the workspace after you publish.
The only exception is a scenario in which two different e-mail
systems are involved, and the e-mails are different enough that the
processing engine can't exactly match them. In the rare case that
this happens, you may see email duplicates in the workspace.
Deduplication - Custodial
Arranges for documents from each processing data source to be de-
duplicated against only documents in data sources owned by that
custodian. Selecting this makes the Propagate deduplication data
field below visible and required. Deduplication is run on custodian
ID's; there's no consequence to changing a custodian's name after
their files have already been published.
Propagate Deduplication Data - What does this mean?
Applies the deduplication fields you mapped out of deduped
custodians, deduped paths, all custodians, and all paths field data
to children documents, which allows you to meet production
specifications and perform searches on those fields without having
to include family or overlay those fields manually. This field is only
available if you selected Global or Custodial for the deduplication
method above.
