Analytics profiles

Analytics profiles apply to email threading and name normalization structured analytics sets. Before creating a structured analytics set for email threading or name normalization, you must create an Analytics profile to map applicable email field settings. Analytics profiles are reusable and transferable, which means you don't have to create a new profile for every new structured analytics set you create.

Note: The Analytics application must be installed in the workspace in order to set the fields on an Analytics profile.

This page contains the following content:

See these related pages:

Read an Analytics profiles scenario

Using Analytics profiles

You're a system admin and you need to create a structured analytics set to help you thread a large email set. One of your firm's clients, a large construction company, recently became involved in litigation regarding the use of materials that they weren’t informed were potentially environmentally damaging when they purchased them from a major supplier. Subsequently, they handed over to you a large group of emails and other documents related to hazardous substances that they suspect are found in their building materials.

You create a new profile with a name of "Email Headers" so that you can easily identify it when selecting a profile to use for your structured analytics set later. Then, because you want to display email threads in an easy-to-read manner for reviewers and other admins looking at this data, you double-check the contents of the fields used in the Email Field Mappings settings.

Once you save this profile, you can select it when you create structured analytics sets.

Creating or editing an Analytics profile

To create a new profile or edit an existing profile, perform the following steps:

  1. From the Indexing & Analytics tab, select Analytics Profiles. A list of existing Analytics profiles displays.
  2. To create a new profile, click New Analytics Profile. The Analytics Profile Layout appears.
  3. Complete or edit the fields on the layout. See Fields. Fields in orange are required.
  4. Click Save to save the profile and make it available for selection.

Fields

The Analytics Profile layout contains the following fields:

Analytics Profile Information

  • Name - the name of the Analytics profile.

Email Field Mappings

Running email threading or name normalization in a Structured Analytics set requires an Analytics profile with mapped email field settings.

Map workspace fields that store metadata appropriate for the following email fields:

Email header fields

  • Email from field – sender’s email address. Acceptable field types are Fixed-length text and Long text.
  • Email to field – recipients’ email addresses. Acceptable field types are Fixed-length text and Long text.
  • Email cc field – carbon copied (Cc) recipients’ email addresses. Acceptable field types are Fixed-length text and Long text.
  • Email bcc field – blind carbon copied (Bcc) recipients' email addresses. Acceptable field types are Fixed-length text and Long text.
  • Email subject field – email subject line. Acceptable field types are Fixed-length text and Long text.
  • Email date sent field – email sent date. The only acceptable field type is date. For accurate results, this field should contain both the date and time.

Email metadata fields

  • Parent Document ID field (required) – document identifier of an attachment’s parent email. Acceptable field types are fixed-length, long text, and whole number. This field should be set on all attachments. If left blank, the attachments won’t have an Email Thread Group or an Email Threading ID and won't threaded with their parent email. For attachments within attachments, the Parent Document ID may be set to the "grandparent" email (the top-level document ID) or the direct parent email, which has its own Parent Document ID set to the top-level parent. The field does not need to be set on emails. For parent emails, the field can be blank or set to its own Document Identifier.
  • If you do not have the parent document ID data, you can run the Populate Parent ID to Child script to populate this field. For more information on running this script, see Relativity Script Library.

    Example 1 of expected format:

    Document EN11 is the parent email. Notice that the Parent Document ID field is unset on EN11 in this example. This yields valid results. Document EN12 is an attachment. The Parent Document ID must match exactly with the Document Identifier of the parent email. In this case, the Document Identifier is the Control Number field. The Parent Document ID of the attachment (EN12) is correctly set to EN11.

    Example 2 of expected format:

    Document EN11 is the parent email. Notice that the Parent Document ID field is set to itself on EN11 in this example. This will still yield valid results. The Parent Document ID of the attachment (EN12) is correctly set to EN11.

    Example of setting that will generate poor quality results:

    The Parent Doc ID is set to the document’s Artifact ID. Because the Parent Document ID of EN12 does not match with the Control Number for EN11, it will not be threaded with its parent email. Additionally, setting Parent Document ID field for EN11 to a value other than its own Document Identifier will cause incorrect results.

  • Attachment name field – file name of the document attachment. This only needs to be populated for child documents and not the parent email. This field is used to display an attachment’s file name and icon in the Email Threading Display visualization field. If you used Relativity Processing, you may use either the File Name or Unified Title. Acceptable field types are Fixed-length text and Long text.
  • Example of expected format:

    In this example, the File Name field is used on the Analytics Profile for the Attachment Name. Notice that for the parent email, EN11, the File Name field is blank. This field is not used for the parent email, whether or not the field is set. A value in the Attachment Name field for a parent email will have no effect on the email threading results as this field is ignored on parent emails. For the attachment, EN12, the field is set to its file name and extension. The Email Threading Display field will be properly filled on EN12.

  • Conversation ID field – Microsoft Conversation index number generated by Microsoft Exchange. This field is an index to the conversation thread of a message which Microsoft uses to order email messages and replies. If provided, email threading uses the Conversation ID to group together emails even when their Extracted Text differs. The Conversation ID is not typically recommended, as inaccurate Conversation ID data can harm email threading results (and even when it works correctly, it can join together very different email conversations). It is recommended to run email threading without mapping this field. For more information, see Email threading and the Conversation ID field. Acceptable field types are Fixed-length, Long text, and Whole Number.