Configure Email Threading in IPRO Analytics

Eclipse's, Analytics Email Threading technology is used to group together a timeline of related emails, allowing reviewers to understand the context and progression of an email conversation. The email threading component allows relationships among a family of emails to be identified, based on its content. Email families are emails that share a common starting email; an email thread represents a single branch of an email family and determines email order within a family.

Email threading can identify email families and inclusive emails for email threads.

A combination of email headers and email body content is used to determine when emails belong to the same thread. Generally speaking, the algorithm is forgiving, to allow for anomalies that can occur, such as timestamp differences generated by different servers. The determination of inclusiveness follows thread identification, and is much more exacting.

Click here to watch the Email Threading video

Email Threading Fields

Required fields

Fields required for email threading analysis are listed in the following table. These fields are created automatically at the time you process email threading.

field created in ipro eclipse	description
IA Email Action	A value indicating the action the sender of the email performed to generate this email. Possible values include: SEND, REPLY, REPLY-ALL, FORWARD, or DRAFT.
IA Email Set ID	All items contain this value, which identifies the email family to which each email belongs. Emails and their attachments all contain the same value.
IA Inclusive	This value indicates a subset of emails in a family that contains all of the text of all emails and their attachments in the family. This value will indicate the reason the email is considered inclusive. Values may be one of the following: MESSAGE: indicates the email has new message content. ATTACHMENT: indicates this email has new attachment content. MESSAGE-ATTACHMENT: indicates this email has new message and attachment content. NONE: indicates this email is not inclusive and its content is contained in one or more emails within the email thread. Inferred Matches: These are emails that did not match the thread exactly, but were similar enough to determine it should be included in the thread. This is most often attributed to confidentiality notices added by the mail server. Another possible reason for an inferred match is when text in the original message was changed in the reply. MESSAGE INFERRED-MATCH: A document that is inclusive because of content AND was found to be a near duplicate of another document in the family. ATTACHMENT INFERRED-MATCH: A document that is inclusive because of an attachment AND was found to be a near duplicate of another document in the family. MESSAGE AND ATTACHMENT INFERRED-MATCH: A document that is inclusive because of content and an attachment AND was found to be a near duplicate of another document in the family. NONE INFERRED-MATCH: A document that is NOT inclusive but is a member of the family because it is a near duplicate of another document in the family. TIP: This value can be used as a sort key to indicate which inclusive emails to read first to speed up review.
IA Email Sort	This field can help you determine the conversational order of an email thread by looking at the extracted text. This value is expressed by a string of numbers, such as"+2+2+3+2-1+0." Each node, including the root node, represents one email sent to perhaps multiple people, and will contain all copies of this email. The first character in a string represents the IA Email Set ID and the root node (parent email) of the entire email tree. The Email Set ID is followed by a "+" symbol if the root email exists in the data set. The Email Set ID is followed by a "-" symbol if the root email does NOT exist in the data set.

Configure Email Threading

1. Start IPRO Eclipse Administration and log in as a user who is a member of the Super Admin group.

2. On the Case Management ribbon, select Eclipse Analytics > Manage Eclipse Analytics E-mail Threading.

3. On the left side of the screen, select the needed managing client and case.

4. In the Meta Data to Send to Analytics area, map the case fields to be analyzed. The information in these fields will be used to identify email threads and related details. Use one of the following methods to map these fields:

   • To automatically map fields click Auto-Map. IPRO Eclipse will map fields based on field name.

   • To manually map fields, for each field, click in the Database Field cell and select the needed field from the list.

5. Select the Environment that will be used to process the documents.

6. In the Documents to Compare field, select one of the following options:

   • For new configurations, select All Documents.

   • To process only documents that appear in a saved search, select the search in question from the drop-down menu.
7. Click the Apply Content Filters checkbox if content filters are needed. For more information on content filters, see Create and Manage Content Filters.

8. Click Process.

   Note: OPEN DISCOVERY Workers will perform the email threading and instantiate an overlay import once complete.

9. Implement email threading as appropriate to your site. For example, you might have reviewers refer to the email thread relationship. See Manage Relationships for details. Or, you might create and save a search for an email-related field.

10. Alert your users to the availability of email threading and how it should be used at your site.

 

Related Topics

Set Up the Relationship Panel to Display Email Threads (Analytics)

Create Full Email Thread Batches for Review (IPRO Analytics)

Create Inclusive Email Thread Batches for Review (IPRO Analytics)

Create Email Thread with Near Duplicate Batches for Review (Analytics)

Email Threading Fields in IPRO Analytics