Minimum Software Version8.15.0 (With Relativity Integration Enabled)
Solution(s)Cases International Cases US Institutions

Through Opus 2’s partnership with Relativity, we have developed a Relativity Connector that is certified for use on both Relativity One and Server 2023–2024 on-premise deployments. The integration allows users to identify relevant documents within the eDiscovery platform and selectively transfer only those necessary for litigation or case preparation. This helps keep your Opus 2 project focused on the most important documents, improving efficiency and organization throughout the legal process.

System Requirements

CapabilitiesSupported Configuration
Supported Relativity VersionsServer 2023 - 2024
Supported EnvironmentsRelativity One
Maximum Documents Per Workspace2,000 Documents Per Run. 20,000 Total.
Relativity TagsMaximum 500 Tags from Relativity

Relativity Connector & REST API

Opus 2 supports Relativity through the use of Relativity’s REST API architecture. Using Relativity’s RESTful conventions, the REST API passes requests to the Services API, which communicates with the Relativity business engine. The REST API uses named pipes for fast, in-memory communication, minimizing latency in calls between the two services.

Diagram 1 - The Relativity Services and Endpoint Architecture, showing how the REST API interacts with the Services API.


Configuring a Connection with Relativity

The Relativity Connector is an optional feature that can be added in Opus 2 Case Management. It enables linking an individual Opus 2 project to a Relativity project, allowing imports of documents—including production files and associated metadata—from Relativity.

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. 

To configure the connector, navigate to the Integrations menu tab in the project settings. You will need the following:

  1. The URL of the Relativity server you’re connecting to.
  2. Authentication credentials (two tokens generated by Relativity: a user ID and a secret). See Relativity Documentation for details on generating these.
  3. The name of the Relativity project from which you want to pull content.
  4. The title of the Saved Search within that Relativity project. This pre-existing Saved Search defines which documents are extracted.
  5. Details of any metadata fields to be mapped from Relativity to Opus 2. You can map specific fields in Relativity to corresponding fields in Opus 2.

Mapping Metadata Fields

After establishing an initial connection, metadata field information can be fetched from the connected Relativity project and mapped to document metadata fields in Opus 2. Make sure the fields you want to map already exist in your Opus 2 project.

Field Types That Can Be Mapped

The following field types can be mapped between Relativity and Opus 2: 

  • Short text
  • Long text
  • Number
  • Single choice
  • Multiple choice
  • Tags
  • Labels
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 for each page of a document. When Opus 2 fetches these images, they are converted to PDFs so that users can work with them as they would any other published document in an Opus 2 project.

  • If a Relativity user has created a production set prior to files being fetched by Opus 2, production images can be pulled instead of or in addition to the original images.
  • Any native files included in the Saved Search can also be sent to Opus 2. Supported file types will be automatically converted to PDF during processing. Unsupported file types remain as original files in Opus 2.
  • Fetching both the production version and the native version of a file causes Opus 2 to publish them as two versions of the same document. The native file is set as the original version, and the production images are set as the most recent version.
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 Relativity connection is configured, you can update your Opus 2 project with new or changed documents from Relativity at any time. Each import operation is logged in the History tab, which shows the date/time of the import, the new files added, and any existing files that were updated.