Editing Coding Layouts

When editing a coding Layout in Relativity when you click on the a multi choice field that has been added to the layout, you'll see that you have the option to specify the number of columns that appear.

So if you set up a radio button list for the field, if you put '1' under Repeat Columns the buttons will be arranged in a single column. If you select '3' they will be arranged in three columns.

Restricting Users' Access to Produced Images

In Relativity you can restrict users' access to produced document images.

1. Go to Administration . . . Workspace Details and click on 'Manage Workspace Permissions' on the console on the right.

2. Click on Object Security and then select the group whose security you want to edit.

3. Set 'Production' to 'NONE' - the cross-out circle.

Now when the user goes into the core reviewer interface he or she will not see the radio button option for produced image next to the option for extracted text.

Conversation Index Parsing in Relativity

As discussed in the Tip of the Night for September 9, 2016, Outlook metadata may contain a Conversation ID which identifies emails from the same thread. The Conversation field itself is the subject line. The Conversation Family is a 44 character alphanumeric code associated with the first email. The Conversation ID or Conversation Index consists of the initial 44 character, plus 10 more characters added for each reply.

Relativity includes a means to parse out the conversation family code, when you are working with data that just contains Conversation index.

Follow these steps to create a transform set for conversation index parsing

1. Create a new fixed length text field on the document object to hold the Conversation Family code.

2. Make the field relational, and set its relational view to 'Family Documents'

3. Create a new saved search for all records for which the Conversation Index (ID) 'is set', or has at least one entry.

4. Click on the Transform Set parent tab and click 'New Transform Set' . Select the saved search as the data sources and choose 'Conversation Index Parsing' as the handler.

5. After saving, click on the Transform Set you've just created and click new in the Transform section.

6. Put the Conversation ID (Index) field which already contains the code as the source field, and the field created in step 1 as the destination field.

On the console run the transform . . .

When the resulting Conversation Family is added to a Document View you can see that the 44 character code is now displayed by itself.