The views expressed in this blog are those of the owner and do not reflect the views or opinions of the owner’s employer. All content provided on this blog is for informational purposes only. The owner of this blog makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site. The owner will not be liable for any errors or omissions in this information nor for the availability of this information. The owner will not be liable for any losses, injuries, or damages from the display or use of this information. This policy is subject to change at any time. The owner is not an attorney, and nothing posted on this site should be construed as legal advice. Litigation Support Tip of the Night does not provide confirmation that any e-discovery technique or conduct is compliant with legal, regulatory, contractual or ethical requirements.
Featured on the ACEDS blog.
Follow me on Twitter and see How-To Videos on my YouTube channel.
New tips for paralegals and litigation support profesionals are posted to this site each night. Click on the blog headings for better detail.
Analytics Profile: Don't Select Outlook Conversation ID
May 30, 2018
The Tip of the Night for September 14, 2016 discussed how Outlook Conversation IDs can be used to group emails from the same thread together in a Relativity workspace. While working with Conversation IDs can be very helpful, note that Relativity recommends that the Conversation ID field not be selected when setting up an Analytics profile for email threading.
If an admin sets up a profile with the Conversation ID field selected, Relativity will group together emails with the same IDs even if their extracted text is different. The Analytics Guide for version 9.5 states that, "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."
Be sure that your admin doesn't the very understandable mistake of selecting a field for each of the email meta data fields in a draft analytics profile: