Text Field Sizes in Relativity

Fields in Relativity can be any one of several types including date, whole number, decimal, currency, single choice, multiple choice, single object, multiple object, and date fields. Very often an admin will set up fields to hold text. Either long text fields to hold the full text of a document, or a field with numerous entries such as an email recipient field, or fixed length text fields to hold other email metadata fields, file names, and document ID numbers.

When using fixed length fields, keep in mind that they have certain limitations. No fixed length text field can hold more than 4,999 characters. If Unicode text is used in the field, the limit is 4,000 characters. Unicode text may be selected for the field so characters in non-Latin alphabets can be used. Unicode can be used for Arabic, Greek, Chinese, Japanese, Korean, Cryllic, Thai, and many other languages. [Only fixed-length text, long text, single choice, and multiple choice fields support Unicode.]

The default length for a fixed length text field is 255 characters, and Relativity recommends that this field be no more than 400 characters.

In addition you need to be sure that all of the fixed length text fields for any single object don't exceed more than 8,060 bytes (or 8KB) in total data size. Check the field usage for an object in order to confirm that this limit is not exceeded.

Searching for 32 character plus strings in dtSearch

Note that the dtSearch index in Relativity is configured so that it will cutoff any words which are longer than 32 characters. For example, this string:

aeccd639e83d0540ba407a252a23e53d1cfe71

. . .is 38 characters long. It appears in the EDRM Enron email data set.

But if you run a dtSearch search to find it in the searchable extracted text of a workspace, you'll get no results.

Modify the search by simply searching for the first 32 characters:

aeccd639e83d0540ba407a252a23e53d

. . . and the document in which it appears will come up in the search results:

It's not necessary to add an asterisk for a wildcard search after the 32nd character.

Resource Scaling in RelativityOne

One of the advantages of RelativityOne is that it performs automated resource scaling - a server is directed to prioritize the completion of certain functions. So if a mass operation is run involving a lot of data, server resources can be increased, and re-directed from other jobs so the mass operation completes sooner. Automated scaling will be performed for:

1. Branding

2. Indexing

3. OCRing

4. PDF mass exports

5. Processing

6. Productions

Relativity provides some very specific information here, on how fast scaling will be implemented for different functions. When a Processing job takes longer than 10 minutes, and there are other jobs in progress, scaling should be initiated within 45 minutes.

If it takes more than 2 hours to run a branding, production, OCR, or mass PDF job, scaling will be performed.