Republishing Errored Files in Relativity

In Relativity Processing, an admin has the ability on the Files tab to see different views with a list of all documents for discovery; deleted files; and errored files before they are deduplicated and published to the workspace. Errored files, such as corrupt files or password protected files, can be republished, but without the extracted text or metadata.

A specific error is stated for errored files, and a separate field will indicate the phase in which the error occurred.

The square icons with a upwards, right pointing arrow in the Details column can be clicked on in order to see specific metadata for each file, and a list of the processing errors for the file and when they took place.

Discovered files can be republished by selecting the option in the mass operations menu.

.PST archives, .ZIP files, and files identified as duplicates cannot be republished. Repulishing must be performed to publish any errored files that have been retried. An overlay will be performed, and only one version of each file will remain.

Deleted files will be excluded from processing.

Getting Office 365 Data into Relativity

Note that RelativityOne can import data directly from Office 365, keeping the data on Azure cloud servers during the import. Office 365's electronic discovery center will export the data from Outlook Exchange, SharePoint, and OneDrive, and Relativity Processing can import it.

Office 365's electronic discovery center will not provide metadata for .pst files, so they need to be imported with Relativity Processing.

RelativityOne Collect can be added as an application in Office 365.

Different metadata fields can be imported from Office 365 into Collect.

Textual Near Duplicate Anomaly

Note that in Relativity it's possible to find a document with a count of only one in the results after running the tally mass operation on the textual near duplicate group field. The reason why is that during an incremental population for the structural analytics set, a new document may have been added that is a near duplicate of, but larger than a previously loaded document. In this case the new document will be marked as the principal document, and the original that it is a near duplicate of will be orphaned.