Email Threading Fields

Required Fields

Fields required for email threading analysis are listed in the following table. These fields can be created automatically (auto-mapped) at the time you configure email threading. When auto-mapping is used, the resulting fields are as listed in the table.

Field

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 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.

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.

Related pages: