Map View

IN THIS ARTICLE:

The top portion is the Map View which represents a visual map of the email thread/conversation with indicators for inclusiveness, duplicates, derived messages, attachments, and conversation branching. The Map View shows the conversation flow and where each document is located in this flow. The number in the middle of each node represents the message level in the email thread. The number near the top of the node next to the paperclip icon represents the number of attachments an email has.

Clicking on a node in the map view jumps to that message in the conversation view below. This also selects all the branches in the map that contain this message, which will be reflected in the conversation view below. To see the entire thread in the conversation below, click on node 1 or click on the blank space in the map view. You can also use area select and control buttons to isolate targeted portions of the map view, which will filter those messages in the conversation view. For large threads with many branches, use the vertical and horizontal scroll bars to view different parts of the thread and the slider to zoom in and out.

Duplicates

An email with one or more duplicates shows as a stacked node in the Map View. When someone sends an email, this creates a copy of this email in the sender's Sent box and in the Inboxes of everyone this email was sent to. Email threading identifies copies of the same email as duplicates; these can be duped out, leaving only one version of the email to review.

Map View legend

Hover over the map view information icon to see the icons for Node, Actions, and Interactions used in the Map View.

For a deeper dive into each node indicator, see the article, Email Threading Details.

Non-inclusive		White means this email is non-inclusive. Non-inclusive emails do not contain unique content.
Inclusive		A blue border means this email is inclusive. Inclusive emails contain unique content.
Duplicates		Stacked documents mean this email has duplicates. Duplicates do not contain unique content.
Derived		Gray means this node was derived. The email this node relates to is not present in the set. For more details, see Derived Nodes below.
Attachments		A paperclip means this email has one or more attachments.
Document has Inline Changes		A red pencil means this email contains inline changes
Duplicates with Inline Changes or Recipient Differences		A red pencil with a plus sign means this email contains a duplicate email with inline changes or recipient differences.

Map View nodes

In the Map View, each node can encompass multiple documents: an email, attachments, and duplicates. In the blue header above the map view, the number of nodes and the number of documents are listed. In the example below, the map view displays 6 nodes, and 22 separate documents are encompassed in these 6 nodes.

Nodes representing a single email without attachments encompass only one document (e.g., Node 6 above). Nodes that represent an email with attachments and/or an email with duplicates will encompass multiple documents (e.g., Nodes 1-4 above). It is also possible for a node to encompass zero documents (e.g., Node 5 above). For more information, see Derived Nodes below.

Node hovers

To see detailed information about all the documents encompassed in a node, hover over the node in the Map View with your mouse.

Node hovers display key information about the documents in that node, including the email's From name, Sent date and time, and the total Participants, as well as the number of participants that joined or left the email thread at this point, information about the email's attachments, duplicate emails, and duplicate attachments, and control numbers for each document in that node. Also available is information about the document location (see below), and content marker information for each document in that node. Click on the control number link to navigate to that document. Click on the pop-out window icon next to the control number to open the document in a new window.

Document location indicators

Document location Indicators show you which document you are on/reviewing in the Thread Viewer. They highlight the document you see behind the Thread Viewer if you slide it down or pop it out into a new window. This document is also updated if you edit any fields in the Relativity layout. The orange highlighting around a node in the map view is one of the primary indicators of the document location. Another indicator is in the Node hover, which shows the document location's control number. If the document you are on is an attachment, the node, and attachment are both highlighted in orange in the map view, along with the control number underlined in the Node Hover. If the document you are on is a duplicate, the node, and stacked outline are both highlighted in orange in the map view, along with the control number underlined in the Node Hover. If the document you are on is a duplicate attachment, the node, the stacked outline, and the attachment are all highlighted in orange in the map view, along with the control number underlined in the Node Hover.

Derived nodes

A derived node/message is a node that does relate back to any document that is present in the set. In the map view, derived nodes are displayed in gray.

In the example above, node 2 is derived. Node 2 relates to a document that does not exist in the set that email threading was run over. Although the document for node 2 does not exist in the set, email threading can still derive information about node 2 from the document in node 3, which does exist in the set. Emails aggregate prior emails when they are sent and received. In the example above, the document in node 3 has aggregated message information from the previous documents in nodes 1 and 2. Node 1 is the original message, node 2 is a forward of the original message, and node 3 is a reply to the forwarded message. Although the document that relates to node 2 does not exist in the set, the document from node 3 is able to derive information about the message in 2.

Node hovers and document location indicators do not exist for derived nodes. In some cases, derived messages can sometimes help identify gaps in collections. These emails existed as separate documents but may not have been collected.