Use Relativity’s processing feature to ingest raw data directly into your workspace for eventual search, review, and production without the need for an external tool. You can use the various processing objects to create custom processing jobs that handle a wide array of information.
Note: Your environment has been enabled to dynamically scale your Invariant worker servers dependent on load. Sustained activity is automatically detected by the system, and Relativity will add workers to handle this work. Once the work is done, they will automatically scale back down. This feature is continually being improved to be smarter about when we add workers and how many we add.
Some of the primary goals of processing are to:
- Discern, at an item level, exactly what data is found in a certain source.
- Record all item-level metadata as it existed prior to processing.
- Enable defensible reduction of data by selecting only items that are appropriate to move forward to review.
Note: There are no specific security requirements, but if a user needs to be restricted from running processing, then permissions need to be revoked to all processing objects.
This page contains the following information:
For a list of changes made to processing per monthly product update, see the Release Notes.
You’re a litigation support specialist, and the lead attorney hands you a CD containing data on a key custodian. There are about 200,000 files on the disc, and he's only looking for files from an 18-month period.
You use Relativity's processing feature to bring in that custodian’s data to Relativity and then to filter it based on what the lead attorney is looking for in this case. To do this, you first save the files into a folder and create a new custodian, Joe Smith.
Then you create a new processing set, to which you add a data source that has only Joe Smith associated with it. This data source includes a source path that is the folder in which you saved the custodian's files.
Once you save the processing set, you can inventory that custodian's data and eliminate all the files that fall outside of the 18-month period you're dealing with. Once you narrow down the data set to the most relevant files, you can
The following steps depict a typical processing workflow that uses all available processing objects and phases. Note that each user's workflow may vary. You may not be required to follow all of these steps for every processing job you run.
- Processing sets
Entities can be created on the fly, in advance, or automatically through imports or connections to HR systems.
Processing Profiles carry over from template workspaces.
If necessary, create new Password Bank Entries with passwords for any password-protected files to be processed.
- (optional) Inventory
Inventoried files can be filtered down based on several metadata attributes prior to publish.
Reports can be run to understand and communicate the files culled from publish.
Post publish – view, ignore, or retry any errors that occurred during any phase of the processing job. If needed, republish the files.
The logging framework enables you to efficiently gather runtime diagnostic information. You can use logging for troubleshooting application problems when you need a very granular level of detail, for example, when working with a Relativity Support representative.
Relativity system components that can log messages are identified based on the system-subsystem-application designation. When troubleshooting, use the system-subsystem-application matrix to configure logging to target a specific Relativity component, such as the Processing application.
Note: It's recommended that you not set your logging to verbose when publishing documents to a workspace, as doing so can cause your worker to run out of resources (CPU, RAM, disk usage, etc.), which then causes your publish job to cease entirely. If you need to use verbose logging in order to collect detailed logs, do so for short periods of time only (under 5 minutes) and have a developer on hand to troubleshoot if any issues occur.