Post-Publication Deletion to Update Processing Results

The post-publication delete function in Relativity allows updates to processing results to be made accordingly after a document has been removed from the active workspace. Post-publication deletions will take place automatically after a delete mass operation has been performed, if and only if the option to delete all associated files is chosen.

You have the option to avoid deleting any documents with tags, redactions, or highlighting.

If some of the deleted documents are primary versions of duplicates not published to the workspace, deduplication will be re-run so a new primary document is published. Duplicates with the same custodian will not be automatically removed.

When a parent document is deleted, the child documents will be marked in the ‘Processing Deletion?’ field with a ‘Yes’, but also with a ‘Yes’ in the ‘Is Published?’ field where the parent document is marked ‘No’.

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.