Email Threading Workflows
BOSTON USER GROUP Workflows for Email Threading
© kCura LLC. All rights reserved.
Jacob Cross
© kCura LLC. All rights reserved.
Overview The objective of today’s session is to give you some ideas that will hopefully increase your knowledge of how email threading works and how to use it to your benefit during reviews.
© kCura LLC. All rights reserved.
Agenda •
Overview of Email Threading
•
Loading New Email into an Existing Thread Set
•
Batching Options
•
Conflict Checks
•
QC with Threading
•
Leveraging Previously Coded Documents
• Questions
Overview of Email Threading
© kCura LLC. All rights reserved.
Overview of Threading •
Based on Text
•
Combines Threads as Email Thread Groups
•
No Index Necessary
•
Identifies Inclusive Emails
© kCura LLC. All rights reserved.
© kCura LLC. All rights reserved.
John emails Jane.
© kCura LLC. All rights reserved.
Jane forwards John’s email to Bob on her iPhone.
© kCura LLC. All rights reserved.
Bob replies to Jane in Outlook.
© kCura LLC. All rights reserved.
Step 1: Find the Segments and Headers
© kCura LLC. All rights reserved.
Step 2: Group the Segments
© kCura LLC. All rights reserved.
Email Threading ID in Relativity
© kCura LLC. All rights reserved.
Step 3: Determine Inclusiveness Non-inclusive
Inclusive
An email whose text and attachments are fully contained in another (inclusive) email.
• An email that contains unique content not included in any other email. • Does not consider recipient information.
© kCura LLC. All rights reserved.
Step 3: Determine Inclusiveness Determined by the following: •
Has the text changed?
•
Have attachments been removed?
Tends to be conservative •
When in doubt, extra inclusives are identified
Inclusive sets are not unique •
Puts the least amount of content in front of the reviewer, while still ensuring that all text variants and all attachments are seen
Considers content only •
Adding or removing recipients does not cause an inclusive flag
© kCura LLC. All rights reserved.
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
© kCura LLC. All rights reserved.
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
© kCura LLC. All rights reserved.
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
EN51
© kCura LLC. All rights reserved.
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
EN51
EN52 EN53
© kCura LLC. All rights reserved.
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
EN55
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
? EN51
EN52 EN53
????
0001+
© kCura LLC. All rights reserved.
EN62
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Determine Inclusive
© kCura LLC. All rights reserved.
EN51 is Non-Inclusive Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
The Attachment Keeps EN52 Inclusive Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
We don’t have the Middle Email Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
EN55 is Non-Inclusive Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
EN62 is Non-Inclusive Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
EN00008de Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Loading New Email into an Existing Thread Set
© kCura LLC. All rights reserved.
Incremental Build What Happens
What Does Not Happen
•
Inserts new emails into existing threads
•
•
Creates new threads, if there are any
•
Determines inclusiveness of new emails
•
Updates duplicate spare
© kCura LLC. All rights reserved.
Change inclusiveness
Incremental Build Example
© kCura LLC. All rights reserved.
Original Example EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Let’s Say We Didn’t Load the Last Email or the Branch EN000018de+
0000+
0000-
0000+
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
EN55
EN55 Is Inclusive as It Is the Last Email in the Thread EN000018de+
0000+
0000-
0000+
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
EN55
Running an Incremental Build
© kCura LLC. All rights reserved.
Newly Loaded Email EN61 Is the Missing Middle Email EN000018de+
0000+
0000-
0000+
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
EN61
EN55
The Segment Is no Longer Missing EN000018de+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
© kCura LLC. All rights reserved.
The Last Email in the Chain Is Added EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
© kCura LLC. All rights reserved.
But EN55 Remains an Inclusive EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
© kCura LLC. All rights reserved.
The Branch Is Added to the Chain and EN62 is Non-Inclusive EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
Results of the Incremental Build EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
Full Build What Happens
Trade Offs
•
•
Time for running the whole set
•
Will lose previous results
As if you were running it all at once
– Because you are
– Could copy into new fields
© kCura LLC. All rights reserved.
Results of the Incremental Build EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN95
EN55
EN56
© kCura LLC. All rights reserved.
EN55 Would Become Non-Inclusive EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
© kCura LLC. All rights reserved.
The Branch Is Added to the Chain and EN62 is Non-Inclusive EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
Final Results of Full Build EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
Delta Between Incremental and Full Build on this Thread EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
Batching Options
© kCura LLC. All rights reserved.
Batching Options Group by email thread group •
Allows reviewers to see all the email from a conversation together
•
Use view to limit to inclusive
© kCura LLC. All rights reserved.
Batch by Thread EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
All 8 Documents (Don’t forget the attachment on the second email)
© kCura LLC. All rights reserved.
Batching Options Group by email thread group •
Allows reviewers to see all the email from a conversation together
•
Use view to limit to inclusive
Only inclusive •
Plus family?
•
Exclude duplicate spares?
© kCura LLC. All rights reserved.
Inclusive Only (Include Family) EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
4 of 8 Documents (Don’t forget the attachment on the second email)
© kCura LLC. All rights reserved.
Batching Options Group by email thread group •
Allows reviewers to see all the email from a conversation together
•
Use view to limit to inclusive
Only inclusive •
Plus family?
•
Exclude duplicate spares?
Using Conceptual Clustering to Batch Inclusive Emails
© kCura LLC. All rights reserved.
Conflict Checks
© kCura LLC. All rights reserved.
Batching Options Think family level conflict checks •
Only bigger
•
All inclusives matching is the most common result
© kCura LLC. All rights reserved.
All Inclusives Coded the Same EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN95
EN55
EN56
0001+
0000+
EN62
EN57
We’ll call green responsive. (Notice that non-inclusive emails are not coded in this example)
© kCura LLC. All rights reserved.
Batching Options Think family level conflict checks •
Only bigger
•
All inclusives matching is the most common result
•
Less likely for the coding to match than families – Review protocols often call for whole families, but not threads to be coded the same
Two common checks •
Where thread has a responsive and a privileged document
•
Where thread has a responsive and non-responsive document
© kCura LLC. All rights reserved.
All Threads That Have at Least One Responsive
© kCura LLC. All rights reserved.
Privilege & Non-Responsive Conflict Check
© kCura LLC. All rights reserved.
Responsive & Privilege in the Same Thread EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
We’ll call red privilege. (Notice that non-inclusive emails are not coded in this example)
© kCura LLC. All rights reserved.
Responsive, Non-Responsive, & Privilege in the Same Thread EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
May still need to code all documents.
© kCura LLC. All rights reserved.
Batching Options Think family level conflict checks •
Only bigger
•
All inclusives matching is the most common result
•
Less likely for the coding to match than families – Review protocols often call for whole families, but not threads to be coded the same
Two common checks •
Where thread has a responsive and a privileged document
•
Where thread has a responsive and non-responsive document
Good to set up at the beginning of review to keep track of review progress © kCura LLC. All rights reserved.
QC Review
© kCura LLC. All rights reserved.
QC Review Using Email Threading •
Including whole thread in QC checks
•
Sample inclusives to focus efforts
•
Focus on threads with multiple designations
© kCura LLC. All rights reserved.
QC Example EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
Leveraging Previously Coded Documents
© kCura LLC. All rights reserved.
Leveraging Previously Coded Documents •
Similar to conflict check – Two search method
•
Look for documents in threads that already have coding – New documents part of thread that was already coded as responsive
– Part of thread with a privileged document • Promote directly to second level?
– In thread with non-responsive • Not as high priority?
© kCura LLC. All rights reserved.
Leverage Previous Coding
0001+
0000+
EN71
EN71
EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
All Threads That Have at Least One Privilege Document
© kCura LLC. All rights reserved.
New Documents That Are in a Thread With a Privilege Document
© kCura LLC. All rights reserved.
Leverage Previous Coding
0001+
0000+
EN71
EN71
EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
QC Review using Email Threading •
Similar to conflict check – Two search method
•
Look for documents in threads that already have coding – New documents part of thread that was already coded as responsive
– Part of thread with a privileged document • Promote directly to second level?
– In thread with non-responsive • Not as high priority?
© kCura LLC. All rights reserved.
Relativity 9.5 Email Thread Visualization
© kCura LLC. All rights reserved.
Email Thread Visualization
© kCura LLC. All rights reserved.
Email Thread Visualization
© kCura LLC. All rights reserved.
In Review Overview of Email Threading
Loading New Email into an Existing Thread Set Batching Options Conflict Checks
QC with Threading Leveraging Previously Coded Documents © kCura LLC. All rights reserved.
Resources Training kcura.com/relativity/resources/training
Relativity Documentation help.kcura.com
Workflow Support [email protected]
Technical Support [email protected] © kCura LLC. All rights reserved.
Questions?
© kCura LLC. All rights reserved.
© kCura LLC. All rights reserved.
Jacob Cross
© kCura LLC. All rights reserved.
Overview The objective of today’s session is to give you some ideas that will hopefully increase your knowledge of how email threading works and how to use it to your benefit during reviews.
© kCura LLC. All rights reserved.
Agenda •
Overview of Email Threading
•
Loading New Email into an Existing Thread Set
•
Batching Options
•
Conflict Checks
•
QC with Threading
•
Leveraging Previously Coded Documents
• Questions
Overview of Email Threading
© kCura LLC. All rights reserved.
Overview of Threading •
Based on Text
•
Combines Threads as Email Thread Groups
•
No Index Necessary
•
Identifies Inclusive Emails
© kCura LLC. All rights reserved.
© kCura LLC. All rights reserved.
John emails Jane.
© kCura LLC. All rights reserved.
Jane forwards John’s email to Bob on her iPhone.
© kCura LLC. All rights reserved.
Bob replies to Jane in Outlook.
© kCura LLC. All rights reserved.
Step 1: Find the Segments and Headers
© kCura LLC. All rights reserved.
Step 2: Group the Segments
© kCura LLC. All rights reserved.
Email Threading ID in Relativity
© kCura LLC. All rights reserved.
Step 3: Determine Inclusiveness Non-inclusive
Inclusive
An email whose text and attachments are fully contained in another (inclusive) email.
• An email that contains unique content not included in any other email. • Does not consider recipient information.
© kCura LLC. All rights reserved.
Step 3: Determine Inclusiveness Determined by the following: •
Has the text changed?
•
Have attachments been removed?
Tends to be conservative •
When in doubt, extra inclusives are identified
Inclusive sets are not unique •
Puts the least amount of content in front of the reviewer, while still ensuring that all text variants and all attachments are seen
Considers content only •
Adding or removing recipients does not cause an inclusive flag
© kCura LLC. All rights reserved.
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
© kCura LLC. All rights reserved.
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
© kCura LLC. All rights reserved.
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
EN51
© kCura LLC. All rights reserved.
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
EN51
EN52 EN53
© kCura LLC. All rights reserved.
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
EN55
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
? EN51
EN52 EN53
????
0001+
© kCura LLC. All rights reserved.
EN62
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Email Thread ID Break Down Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Determine Inclusive
© kCura LLC. All rights reserved.
EN51 is Non-Inclusive Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
The Attachment Keeps EN52 Inclusive Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
We don’t have the Middle Email Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
EN55 is Non-Inclusive Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
EN62 is Non-Inclusive Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
EN00008de Control Number
Email Threading ID
EN56
EN000018de+0000+0000-0000+0000+
EN63
EN000018de+0000+0000-0001+0000+
EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Loading New Email into an Existing Thread Set
© kCura LLC. All rights reserved.
Incremental Build What Happens
What Does Not Happen
•
Inserts new emails into existing threads
•
•
Creates new threads, if there are any
•
Determines inclusiveness of new emails
•
Updates duplicate spare
© kCura LLC. All rights reserved.
Change inclusiveness
Incremental Build Example
© kCura LLC. All rights reserved.
Original Example EN000018de+
0000+
0000-
0000+
0000+
EN55
EN56
0001+
0000+
EN62
EN63
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
Let’s Say We Didn’t Load the Last Email or the Branch EN000018de+
0000+
0000-
0000+
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
EN55
EN55 Is Inclusive as It Is the Last Email in the Thread EN000018de+
0000+
0000-
0000+
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
????
EN55
Running an Incremental Build
© kCura LLC. All rights reserved.
Newly Loaded Email EN61 Is the Missing Middle Email EN000018de+
0000+
0000-
0000+
? EN51
© kCura LLC. All rights reserved.
EN52 EN53
EN61
EN55
The Segment Is no Longer Missing EN000018de+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
© kCura LLC. All rights reserved.
The Last Email in the Chain Is Added EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
© kCura LLC. All rights reserved.
But EN55 Remains an Inclusive EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
© kCura LLC. All rights reserved.
The Branch Is Added to the Chain and EN62 is Non-Inclusive EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
Results of the Incremental Build EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
Full Build What Happens
Trade Offs
•
•
Time for running the whole set
•
Will lose previous results
As if you were running it all at once
– Because you are
– Could copy into new fields
© kCura LLC. All rights reserved.
Results of the Incremental Build EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN95
EN55
EN56
© kCura LLC. All rights reserved.
EN55 Would Become Non-Inclusive EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
© kCura LLC. All rights reserved.
The Branch Is Added to the Chain and EN62 is Non-Inclusive EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
Final Results of Full Build EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
Delta Between Incremental and Full Build on this Thread EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
Batching Options
© kCura LLC. All rights reserved.
Batching Options Group by email thread group •
Allows reviewers to see all the email from a conversation together
•
Use view to limit to inclusive
© kCura LLC. All rights reserved.
Batch by Thread EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
All 8 Documents (Don’t forget the attachment on the second email)
© kCura LLC. All rights reserved.
Batching Options Group by email thread group •
Allows reviewers to see all the email from a conversation together
•
Use view to limit to inclusive
Only inclusive •
Plus family?
•
Exclude duplicate spares?
© kCura LLC. All rights reserved.
Inclusive Only (Include Family) EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
4 of 8 Documents (Don’t forget the attachment on the second email)
© kCura LLC. All rights reserved.
Batching Options Group by email thread group •
Allows reviewers to see all the email from a conversation together
•
Use view to limit to inclusive
Only inclusive •
Plus family?
•
Exclude duplicate spares?
Using Conceptual Clustering to Batch Inclusive Emails
© kCura LLC. All rights reserved.
Conflict Checks
© kCura LLC. All rights reserved.
Batching Options Think family level conflict checks •
Only bigger
•
All inclusives matching is the most common result
© kCura LLC. All rights reserved.
All Inclusives Coded the Same EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN95
EN55
EN56
0001+
0000+
EN62
EN57
We’ll call green responsive. (Notice that non-inclusive emails are not coded in this example)
© kCura LLC. All rights reserved.
Batching Options Think family level conflict checks •
Only bigger
•
All inclusives matching is the most common result
•
Less likely for the coding to match than families – Review protocols often call for whole families, but not threads to be coded the same
Two common checks •
Where thread has a responsive and a privileged document
•
Where thread has a responsive and non-responsive document
© kCura LLC. All rights reserved.
All Threads That Have at Least One Responsive
© kCura LLC. All rights reserved.
Privilege & Non-Responsive Conflict Check
© kCura LLC. All rights reserved.
Responsive & Privilege in the Same Thread EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
We’ll call red privilege. (Notice that non-inclusive emails are not coded in this example)
© kCura LLC. All rights reserved.
Responsive, Non-Responsive, & Privilege in the Same Thread EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
May still need to code all documents.
© kCura LLC. All rights reserved.
Batching Options Think family level conflict checks •
Only bigger
•
All inclusives matching is the most common result
•
Less likely for the coding to match than families – Review protocols often call for whole families, but not threads to be coded the same
Two common checks •
Where thread has a responsive and a privileged document
•
Where thread has a responsive and non-responsive document
Good to set up at the beginning of review to keep track of review progress © kCura LLC. All rights reserved.
QC Review
© kCura LLC. All rights reserved.
QC Review Using Email Threading •
Including whole thread in QC checks
•
Sample inclusives to focus efforts
•
Focus on threads with multiple designations
© kCura LLC. All rights reserved.
QC Example EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
Leveraging Previously Coded Documents
© kCura LLC. All rights reserved.
Leveraging Previously Coded Documents •
Similar to conflict check – Two search method
•
Look for documents in threads that already have coding – New documents part of thread that was already coded as responsive
– Part of thread with a privileged document • Promote directly to second level?
– In thread with non-responsive • Not as high priority?
© kCura LLC. All rights reserved.
Leverage Previous Coding
0001+
0000+
EN71
EN71
EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
All Threads That Have at Least One Privilege Document
© kCura LLC. All rights reserved.
New Documents That Are in a Thread With a Privilege Document
© kCura LLC. All rights reserved.
Leverage Previous Coding
0001+
0000+
EN71
EN71
EN000018de+
0000+
0000+
0000+
0000+
EN51
EN52 EN53
EN61
EN55
EN56
0001+
0000+
EN62
EN63
© kCura LLC. All rights reserved.
QC Review using Email Threading •
Similar to conflict check – Two search method
•
Look for documents in threads that already have coding – New documents part of thread that was already coded as responsive
– Part of thread with a privileged document • Promote directly to second level?
– In thread with non-responsive • Not as high priority?
© kCura LLC. All rights reserved.
Relativity 9.5 Email Thread Visualization
© kCura LLC. All rights reserved.
Email Thread Visualization
© kCura LLC. All rights reserved.
Email Thread Visualization
© kCura LLC. All rights reserved.
In Review Overview of Email Threading
Loading New Email into an Existing Thread Set Batching Options Conflict Checks
QC with Threading Leveraging Previously Coded Documents © kCura LLC. All rights reserved.
Resources Training kcura.com/relativity/resources/training
Relativity Documentation help.kcura.com
Workflow Support [email protected]
Technical Support [email protected] © kCura LLC. All rights reserved.
Questions?
© kCura LLC. All rights reserved.
