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.
Note the line in a Relativity email thread summary which lists email threads for which no root was found.
This indicates that there are differences in the extracted text for some email threads. Don’t overlook these when focusing on inclusive emails. They may be an indication that an email recipient altered someone’s message - whether to answer a serious of questions with an inline response, or for some nefarious purpose.
When working with a conceptual index for Relativity analytics, there are different circumstances when the training set, the searchable set, and the index should be updated.
When documents with new concepts are added, these documents should be added to both the training set [from which term relationships are learned] and the searchable set [on which the analytics tools like clustering and categorization are run]. Perform an incremental build on the index.
When documents with no new concepts are added, these documents should be added to the searchable set. Perform an incremental build on the index.
When documents that make up more than 10-30% of the entire set are added, these documents should be added to both the training set and the searchable set . Perform an incremental build on the index.
When documents that make up less than 10-30% of the entire set are added, these documents should be added to the searchable set. Perform an incremental build on the index.
When documents are removed from a training or searchable set, an incremental index build should be performed.
When new words are added to the list of concept stop words, the index should be deactivated and then rebuilt.
When extracted text is modified, perform a full build on the index.
When email header and repeated content filters are revised, perform a full build on the index.
When email threading is performed in Relativity, the analytics server can detect more segments than there are blocks in an Email threading ID. This will be an indication that the latest email matches an earlier segment. If the ID has more blocks than detected segments, the segments may have been edited or corrupted.
Segments are calculated by the number of indentation levels. Relativity uses indentation squares like this to show the number of indentation levels.
When a server applies a confidentiality footer, it can cause the email threading ID to get an extra block. So even though there would in fact be three segments in an email the ID would look like this: F00000abc-0000- 0000+0000+.