Frequently Asked Questions

No. For search, concept groups and Predictive Coding, only the chat or email content is used; noise information is ignored.

The easiest way is to search for the document on the Analysis or Review page, and then click the duplicate icon for a document.

In associated document views, this icon is not available. If you do not want to go back to the Review or Analysis page, you can use the document metadata. To do so, display the document in the viewer and click in the viewer toolbar. This opens the Metadata fly-in.

If documents have an MD5 hash

Compare the MD5 hash.

For email items, i.e., emails, calendar entries, contacts, tasks, etc.

First check the sent date, from and to addresses and subject. If these are all identical then check the content.

Yes. You can configure your view to display the sender.

1. Open a thread in associated results view.
2. Click the toolbar button to expand the configuration options.
3. Click Configure.
4. Make the appropriate selection from the column display options (available options can differ depending on your matter settings).

If content analysis is used for thread detection, emails that have the same author, sent date and content have the same thread hash value. This can cause them to be displayed together as if they are part of an email thread even when one of the emails is not contained in the other. This typically occurs when the body of the emails is empty or contains a standard message. Review each email individually.

If content analysis is used for thread detection, the hash value used for thread detection is based on consistent date and subject information. If one mail contains a sent date with a time zone and another does not or has missing date information, the computed hash values are not comparable and the emails are not identified as being part of the same email thread. The same holds true if the subject of a related email was changed.

Also, if one of the senders did not use the standard reply function provided by most of the common email systems, but deleted some content of a preceding email, or used inline reply, emails are no longer identified as belonging to one thread. This makes sure that reviewers do not miss any differences.

A grayed out document preceded by an icon indicates a duplicate of that document exists in a thread or family. The document is not necessarily a duplicate of another document in the thread or family you are currently viewing.

For more information, please see the related topics.

Related:

Email Threads and End of Branch Email

Thread Detection by Header Analysis

Families

A grayed out document preceded by an icon indicates a duplicate of that document exists in a thread or family. The document is not necessarily a duplicate of another document in the thread or family you are currently viewing.

For more information, please see the related topics.

Related:

Email Threads and End of Branch Email

Thread Detection by Header Analysis

Families

Only Case Managers and Admin users can delete fields and field values and you may not be assigned one of those user roles.

Another reason may be that the field or field value is associated with a tagging rule. To ensure tagging rules are respected:

• Field values used for a tagging rule cannot be deleted.
• Fields used for a tagging rule cannot be deactivated.
• Fields used for a tagging rule cannot be removed from the arrangement or be made read-only.

To determine whether a field or field value is part of a tagging rule, navigate to the AdministrationArrangements page. Review the Fields Used column to determine which arrangement(s) the field is used in. Open the identified arrangement and navigate to the Tagging Rules tab to review the rules and fields used.

If Hypergraph is empty, consider these potential reasons:

• Hypergraph evaluates only email and chat communication. If search or filter criteria is applied, the search results may not contain any email or chat communications.
• Hypergraph needs at least these metadata fields to display a document: Sender name (meta_fromname) and Recipient name (meta_recipient) OR Sender Domain (meta_fromdomain) and Recipient Domain (meta_reciepientdomain). If your data was CSV loaded, are these fields populated?
• Check your Hypergraph display settings to see whether you are viewing Hypergraph using the sender, recipient or domain fields. The documents in the data set you are viewing may not have the selected fields populated.

Yes, see here: How to Generate Good Phrases

At this time, production export settings can only be reused within a specific matter. To do this, configure your first production export. When you prepare the export for your next production, open the Export Production wizard and select the original export in the Copy Configuration field. This updates the current export to match the settings of the selected export. You can then update individual setting if needed.

You cannot share a saved search with specific individual users. Sharing a saved search makes the query available to all users working in the matter.

See here: What Do the Specific Smart Filters Do?

Yes. Use care when text fields exist in a tagging arrangement and you are bulk tagging documents. The content of a text field may be replaced, not appended.

Example: A user adds a note to a Review Comment text field. You later review the document's family members and decide to add a note to the Review Comment field for the entire family. Your note will replace the note previously added by the other user. If you bulk tag the family and do not add content to the Review Comment field, the existing note stays intact.

Yes. Use care when text fields exist in a tagging arrangement and you are using quick tags to apply tags to documents. The content of a text field is replaced, not appended.

Example: A user adds a note to a Review Comment text field. You later review the same document and apply a quick tag (e.g., the L tag), which does not contain text in the Review Comment field. The note added by the other user is deleted. If the Quick Tag contains text in the Review Comment field, the quick tag text replaces the note previously added by the other user.

If you are in Near Native view, and the viewer is slow, this is usually because the document is in the process of being converted. Conversion starts for any unconverted document when you open the Near Native view.

Tip: Ask your project manager to pre-convert documents that will be reviewed. In the meantime, view the document using Text view, which does not require conversion.