| Minimum Software Version | 8.15.0 |
| Solution(s) | Cases International ✓ Cases US ✓ Institutions ⨉ |
Relativity is a review platform that is used to handle the triage and classification of large volumes of documents often resulting from an e-discovery exercise. Typically, only a small subset of these are needed for conducting the case. The Opus 2 Relativity integration is designed to allow a user to easily import that subset into the Opus 2 Platform. Often the case management work may start before the review stage is complete, so the connector also allows content in the Platform to be updated from Relativity after the initial import.
The Relativity integration allows for native documents, production files and associated metadata to be imported into a project. Appropriate folders and associated metadata need to be configured in the connected project before transferring files.
The ability to integrate Relativity with a project is an optional, operator controlled feature. It has been developed specifically for the Opus 2 Case Management solution, but can be made available for any template or solution if desired.
Enabling Relativity integration in a project
Before an integration with Relativity can be set up, the feature must be enabled by Opus 2 Platform Support.
Configuring a connection with Relativity
The Relativity Connector is an optional feature that can be added. It enables the connection of an individual project to a Relativity project and allows for the import of documents from Relativity, including production files and selected associated metadata.
User Permissions Required on Relativity One.
The following workspace Security options must be set for the User being impersonated. Failure to enable these settings prevents the integration from running on the Opus 2 Platform.
Other Settings
Browsers
- Advanced & Saved Searches must be selected.
Mass Operations
- Export and Export to File must be selected.
Object Security
Document
- Document Permission Local Access (Download, Copy Text) must be enabled.
User Permissions Required on Relativity Server:
(Object Security) Document:
- Local Access (Download, Copy Text)
Tab Visibility:
- Documents
(Other Settings) Browsers:
- Advanced & Saved Searches
(Other Settings) Mass Operations:
- Export to File
The following workspace Security options must be set for the User being impersonated. Failure to enable these settings prevents the integration from running on the Opus 2 Platform.
Other Settings
Browsers
The Relativity connector must be enabled on your template before it can be configured. Please check with your account manager to confirm that you have access.
A new integration with Relativity must be configured via the Integrations menu tab in the Project settings. The following information is required in order to establish a connection:
- The url of the Relativity server a connection is being set up with.
- The authentication credentials. These are two tokens, generated by Relativity, consisting of a user id and a secret.
- The name of the project within Relativity from which content should be pulled.
- The title of the Saved Search within that project. This should already have been set up within Relativity and defines the documents that should be extracted.
- Details of any metadata that should be mapped from Relativity to the project. The configuration dialog allows for the individual mapping of specific fields in Relativity to matching field types in the Opus 2 project.
Mapping metadata fields
Once an initial connection with Relativity has been set up, information about metadata fields can be fetched from the connected project and mapped onto document metadata fields in the receiving Opus 2 project. These fields need to be created in the relevant project in advance of being mapped.
The following field types can be mapped between Relativity and Opus 2:
- Short text
- Long text
- Number
- Single choice
- Multiple choice
- Tags
- Labels
Note: It is not possible to map multiple Relativity fields to single metadata fields in an Opus 2 project, each mapping relationship requires a unique field.
Transferring and processing files from Relativity
Relativity's imaging engine creates .tiff images of each page in a document. When these images are brought into a project they are converted to .pdfs so that a project user can work on them similarly to any other document that has been published in an Opus 2 project. Sometimes a Relativity user has to create a production set within Relativity prior to these being fetched by Opus 2. If this is the case, the production images may be fetched instead of or as well as the original file images.
In addition to fetching production and original images, any native file that is included in a Saved Search can be sent from Relativity to an Opus 2 project. Users may choose to receive all native file types, or only those with specified extensions. If the native files are of a type that the Opus 2 service can convert to .pdf in order to create a published document, this happens automatically when the files from Relativity are being processed. If the native files are of a type that cannot be converted to .pdf, they remain as original files within Opus 2.
If a user chooses to fetch both a production version and a native version of a file, the two files are published as two versions of the same document in an Opus 2 project. The native file is set as the original version and the Relativity production image as the most recent version.
Note: Once files from Relativity have been processed and turned into documents in an Opus 2 project, it is necessary to run OCR on any documents containing text in order for this text to be available for highlighting and annotation. The production images that are sent from Relativity come in .tiff format, a file type which does not contain machine readable text.
Import history
Once a connection to Relativity has been configured, a user can update the project with files from Relativity at any time. Each import operation is recorded in the history tab. This shows when the import operation was run and which new files were brought in as well as which files were updated.
Related articles