Searching for symbols in Relativity

You can modify a dtSearch index to make it possible to search for symbols in a Relativity workspace.

1. Under Index Admin, select Search Indexes. Edit a dtSearch index.

2. Scroll down to the Alphabet section and below where is says "[Letters] // Original letter, lower case, upper case, unaccented" enter the symbol you want to search for four times preceded by a space each time. Begin with a leading blank space but do not end with a blank space. For example: % % % %

3. Scroll down within the alphabet section and under the [Ignore] subsection remove the symbol:

. . . some symbols may be in the [Spaces] or [Hyphens] subsections.

4. Rebuild the dtSearch index.

If you're searching for a percent symbol % you need to run a RegEx search in the dtSearch index using this format:

"##75\u0025"

. . . the u0025 signifies the unicode character for the percent symbol. %

dtSearch in Relativity to exclude docs including your search term

Don't miss that in Relativity you can run a dtSearch which will exclude documents where a search term appears in a longer phrase. Use the NOT operator together with the proximity operator set to zero.

Simply follow the search term with: NOT w/0

. . . and then enter the phrase or phrases you don't want to appear in the search results.

This search will turn up documents where 'confidential' appears in the body of an email or document, but not in a disclaimer frequently found at the bottom of an email.

Relativity and JVM RAM

You can improve the performance of Relativity analytics operations by increasing the amount of RAM available for Java. The Java heap is the amount of memory allocated to the Java Virtual Machine (JVM). The JVM is a program that executes other programs written in Java.

Relativity recommends that servers which are used for indexing and structured analytics allocate about 50% of available RAM to Java. This setting should be increased to 75% if only structured analytics is being performed. Only a third of total RAM should be assigned to the Java heap if a server is used only for indexing.

A server will need an amount of RAM in bytes equal to 6000 times the number of documents involved in an index build. So, a training set of a million documents for an index build will require 6 GB of RAM. The same equation applies for calculating the Java heap size needed for a structured analytics set.