With the Production application you can prepare relevant and non-privileged documents to turn over to opposing counsel after review. Relativity's production application makes it easy to customize your productions from placeholders to custom branding.
Note: If you are upgrading to Relativity 10.3 from a previous version of Relativity, consider the Production upgrade considerations in the Relativity Upgrade Guide before you begin your upgrade.
This page contains the following sections:
For more information about working with productions, see the following pages:
- Production queue
- Branding queue
- Importing a production file
- Exporting a production set
- Production sets
- Production console
- Production errors
- Production data source
- Production Placeholders
Also see these related recipes:
- Locking produced documents from editing
- Displaying production fields in a layout
- Importing productions in Relativity as Natives
- Loading external productions into Relativity
- Maintaining previous Bates numbers between production sets
- Overlaying in the production object
- Performing QC of Productions
- Using tokens to customize stamps in a production
For information about troubleshooting the production application through the Service Host Manager, see Service Host Manager in the system guides section.
You're a system admin, and you've just completed a document review project for a client, a healthcare provider, that has been involved in litigation related to inadequate protection of private patient information. After coding all the documents for issues and responsiveness and redacting any sensitive patient information that occurred in those documents, it's time to produce these documents and submit them to the presiding judge.
To do this, you create a new production that defines these documents. You name it Patient Privacy Production and you select the Patient Privacy markup set you created and had your reviewers apply to the sensitive patient information they encountered in the documents they reviewed. For the Production numbering field, you select Page level numbering and enter a prefix of "PPP." Just to reduce the number of characters on each document, you change the number of digits for document numbering field from 7 to 5. You then specify the begin and end Bates number fields, leave the other fields at their defaults and save the new production set.
(click on image to expand)
You then use the options on the production console of the saved production set to
Production application upgrades occur concurrently with Relativity product updates. You can find information about production updates in the Relativity release notes and What's new.
To upgrade the application, use one of the following methods:
- Upgrade to the latest Relativity product update - Upgrading to the latest Relativity update automatically upgrades production to the latest version.
- Upgrade production only - Download the newly released RAP file from the
Relativity Communityand import it into the Application Library.
In order to produce documents, ensure you use the following workflow to create the necessary production components. Use the links in the image below for more information on each part of the production workflow.
The production information object stores important information about your production. Staging a production populates this object in your workspace. As an example, the production information object is useful when you want to look at the amount of documents with redactions, the control number of the documents in your production, which documents were produced with a placeholder, and which documents were produced as a native. The production information object also stores the automatically created Bates numbers associated with the production. Because the Bates numbers automatically populate on production documents, the Bates numbers fields automatically clear when you delete productions.
To quickly view the information stored on this object, click View Documents in the production console. The View Documents pop-up displays information on both documents and individual pages. You can also view information about the documents produced by looking at the saved search that is automatically created when the production job finishes.
Once you run a production, you can view the aforementioned information on the documents list for each produced document by adding the fields to a view and then creating a tab from that view.
As of 184.108.40.206 you can rename any produced production. You will also see the updated on the reflected field Production::ProductionSet on the documents. Furthermore, Production::ProductionSet replaced Production::ProductionName on the document object. As a result, the Production::ProductionName field on the document object was removed.
The following changes were also made to the ProductionInformation object in the Production Application:
- ProductionName field is removed.
- ProductionSet field is now open to association.
The Production Disabled layout is not read-only for the ProductionName field anymore.
Any views, layouts, saved searches, pivots or any RDO that reference the Production Information::ProductionName field will be modified during the upgrade process. Instead, those items will point to Production Information::ProductionSet field. Those views, layouts, saved searches, pivot and RDOs will work as expected after the update.
Tools to assess upgrade impact
You can run a SQL script before updating Relativity to the version that supports Production Renaming to identify possible areas of their application involved in this change. The script will detect all Workspaces, Views, and Saved Searches that use the Prodution::ProductionName either as a field, as a search condition, or as a field for sort order. The script will return the WorkspaceID, name of the affected Object (view, SavedSearch) and whether the impact is a field, view, list, search conditions, or sort option. You can use the outcome of this script to verify the functionality of those areas after performing the upgrade. This script is available here on the Relativity Community.