Changing the Location of an Analytics Index

An admin can change the location of an analytics index or a structured analytics set from their original location on a server. The indexes and structured analytics sets must be in the same location, and only one location can be used for both. While the move occurs, analytics operations cannot be run.

On the server, the admin has to log into Analytics REST (Representational State Transfer). REST is an API which can be used to create applications, and to access resources using template URLs. Template URLs provide a means to re-write HTML content.

Before proceeding with the relocation, the Content Analyst (CAAT) Relativity Analytics Engine Window service must be stopped.

The data may or may not be stored in a single date directory mode. The admin will be able to determine which mode it is in using REST. If it is in single data directory mode the device will be designated single-data-directory.

When data is in single data directory mode, the indexes and sets are copied from the original location to the new location - including any empty folders. The complete structure must be maintained. The new location should have a folder named .ufx; a file named '.initialized', and folders for prior indexes and sets:

In the C:\CAAT\etc directory, a file named 'single-data-dir.properties' will have to be edited so that the new index location is referenced.

If it is not in single data directory mode, the full contents, with subfolders, of these locations on the server:

• C:\CAAT\data-default

• C:\CAAT\indexes;

• C:\CAAT\staging)

. . . must be copied to the new location. A number of steps must be taken but in general the link at C:\CAAT\device-links is deleted, and a new index location is designated.

Limits of a Relativity Analytics Index

Note that when an analytics index is populated in Relativity, preprocessing is performed which affects how the content of the sources for the index in saved searches are used in the index.

In addition to the filters selected on the Analytics Index Information form filled out when the index is created, which can remove email headers, footers, and signatures, and stop words which are too used too often . . .

. . . numbers and symbols will be excluded from the index. The text will also not be case sensitive. All of the searchable text will be lowercase.

Draft Emails Are Inclusive

Email threading is performed in order to avoid the need to read the separate parts of long email threads over and over again.

Relativity defines inclusive emails as those which must be reviewed- they include all of the content for a thread. Non-inclusive emails do not need to be reviewed - but note that the threading analysis does not take the email headers into account.

Duplicate spares are emails which contain the same content as other emails and so do not need to be reviewed.

DRAFT emails are an anomaly. Draft messages are never treated as duplicate spares. They will always be marked as inclusive, and be considered unique content.

Draft emails have this icon with a pencil in the email threading visualization:

So if you have these added to a review don’t think it means they were never sent!