2RelativityOne - Collect - Google Workspace

Relativity Collect - Google
Workspace
January 20, 2023
For the most recent version of this document, visit our documentation website.
Table of Contents
1 Collect 4
2 Installing Collect 5
2.1 System requirements for Collect 5
2.2 Installing Collect 5
2.2.1 Installing Collect from the Application Library to a workspace 5
2.3 Permissions to run Collect 6
3 Matters 8
3.1 Matters 8
3.1.1 Creating a matter 8
3.1.2 Matter Details layout fields 8
3.1.3 Viewing or editing matter details 9
4 Custodian targets 10
4.1 Custodians 10
4.2 Fields 10
4.3 Creating a custodian target 11
4.3.1 Generating targets in the wizard 12
4.4 Removing custodian targets 12
4.5 Target status 12
4.5.1 Reviewing collection targets 12
5 Google Workspace setup 13
5.1 Google Workspace credentials setup 13
5.1.1 Creating a Google Cloud project 13
5.1.2 Enable required APIs for the Project 13
5.1.3 Setup OAuth2 consent screen 14
5.1.4 Create credentials 16
5.2 Google Workspace user account setup 18
5.2.1 Create admin role for Vault API 18
5.2.2 Create admin role for the user accounts listing 19
5.2.3 Create admin role for the groups listing 20
5.2.4 Enable required privileges 20
Relativity Collect - Google Workspace 2

5.3 Restricting collections to the selected user accounts 21
5.3.1 Create an organizational unit 21
5.3.2 Scope user privileges to the organizational unit 22
5.4 Setting up a Google Workspace data source 23
5.4.1 Creating a Google Workspace data source 23
6 Creating a collection data source 25
6.1 Creating a collect data source 25
6.1.1 Data source types and properties 26
7 Collect tab 27
7.1 Creating a collection 27
7.1.1 Using the Collect wizard 27
7.2 Viewing or editing collection details 41
7.2.1 Storing collected data 42
7.2.2 Viewing collected data 43
7.3 Collect console 43
7.3.1 Start Collection 43
7.3.2 Stop Collection 43
7.3.3 Retry Collection 43
7.3.4 Create Processing Job 43
7.3.5 Clone Collection 44
7.3.6 Reports 44
8 Collect reports 45
8.1 Running reports 45
8.1.1 Collection Summary report 45
8.1.2 Collection Details report 45
8.1.3 Results report 45
8.1.4 Errors report 45
9 Collect Store 47
9.1 Moving collected data into storage 47
9.2 Exporting collected data 47
10 Monitor 48
11 Index 50

1 Collect
Collect is an easy-to-use application for collecting your custodian's data through different sources. Start by
setting up Collect as an application within your data source. For information on registering an app, see the
source's documentation on their website. Once registered, start adding custodians, data sources, and
targets to Collect. Once connected, start the collect job and begin collecting data from custodians.
Note: This document covers the Google Workspace source.
n Google Workspace—collect documents from Chat, Drive, Gmail, and Groups. A license for Vault is
required to collect data from Google Workspace. For more information, see Google's Vault
Help documentation.. Google Chat is collected as RSMF files. For more information on short mes-
sages, see the Relativity User site.

2 Installing Collect
You can easily install Collect in a workspace by using the functionality available through the Application
Deployment System (ADS). This system provides you with the option to install Collect by selecting it from
the list of existing applications in the Application Library tab or by importing it from an external application
file.
To install Collect, perform the following procedures:
1. Install Collect from the Application Library. See Installing Collect below.
2. Enable access for the data source.
2.1 System requirements for Collect

Collect uses the ADS framework, so you install it as an application within a Relativity instance.
Consequently, Collect has the same system requirements as RelativityOne. For RelativityOne's system
requirements, see System Requirements on the RelativityOne Documentation site.
Note: Confirm that you have the appropriate system admin permissions to install an application. For more
information, see Workspace security on the RelativityOne Documentation site.
2.2 Installing Collect

Collect is compatible with RelativityOne. See Getting started in RelativityOne on the Documentation site for
requirements. Note that for a Collect-only installation, you do not need the following pre-requisities:
n Analytics server setup

n Database server for processing or native imaging
n Worker server for processing or native imaging
n Obtaining applications for native imaging and processing
Because Collect uses the ADS framework, you can install through the Relativity Application tab from the
library. See Installing Collect from the Application Library to a workspace below.
Note: You configure security permissions on Collect just as you would for any other Relativity application.
For more information, see Workspace security on the Relativity RelativityOne Documentation site.
2.2.1 Installing Collect from the Application Library to a workspace

If Collect is in the Application Library, you can install it to the current workspace. Confirm that you have the
appropriate system admin permissions to install an application. For more information, see Workspace
security on the RelativityOne Documentation site.
Note: Analytics, Case Dynamics, Collect, Legal Hold, and Processing all share the Entity object. You may
be prompted to complete additional steps to unlock and resolve conflicts of the listed applications in order
to complete installation. For information, see Troubleshooting application installation errors on the
Relativity Beta Documentation site.
Use the following procedure to install Collect from the Application Library:

1. Navigate to the workspace where you want to install the application.
2. Navigate to the Application Admin tab.
3. Click New Relativity Application to display an application form.
4. Click the Select from Application Library radio button in the Application Type section.
5. Click in the Choose from Application Library field.

6. Select Collect on the Select Library Application dialog. This dialog only displays applications added to
the Application Library. If Collect is not included in the list, see the Installing applications topic.
7. Click Ok to display the application in the Choose from Application Library field. The application
form also displays the following fields:
n Version - displays the version of the application that you are installing.
n User-friendly URL - displays a user-friendly version of the application's URL. This field may
be blank.
n Application Artifacts - displays object types and other application components.
n Map Fields - There are no fields available in Collect for mapping.
8. Click Import to install Collect into the workspace.
9. Review the import status of the application. Verify that the install was successful or resolve errors.
2.3 Permissions to run Collect

The following security permissions are required to run and complete the collection process:

Object Security Tab Visibility Other Settings
n Collection – View, Edit, Add n Entities n None

n Collection Detail Custodian – View, Edit, n Collect
Add o Matters
n Collection Detail Custodian Target – View, o Custodian Targets
Edit, Add
o Collections
n Collection Detail Custodian Target Result
– View, Edit, Add
o Status Summary
n Collection Detail Request – View, Edit, Add

o Target Status
n Collection Detail Source Instance – View,

o Collection Admin
Edit, Add o Monitor
n Collection Detail Source Type – View, Edit,
Add
n Collection Detail Summary – View, Edit,
Add
n Collection Matter – View, Edit, Add
n Collection Source Instance – View, Edit,
Add
n Collection Source Instance Parameter –
View, Edit, Add
n Collection Source Type – View, Edit, Add
n Collection Source Type Parameter Type –
View, Edit, Add
n Collection Source Type Criteria – View,
Edit, Add
n Custodian Target – View, Edit, Add
n Entity – View, Edit, Add
n Custom – View, Edit, Add

3 Matters
In Collect, a matter represents a legal action or case requiring you to collect electronic data from sources
such as Google Workspace. Matters can be used to group multiple related collection jobs.
3.1 Matters
You manage matters that are associated with a collection. You can create each of these items on their
respective tabs, or you can create them when you add a new collection.
Note: Matters created from Home aren't available for use in Collect nor listed on the Matters tab in this
application. Additionally, the matters created on this tab are only available for use in Collect.
3.1.1 Creating a matter

Use the following procedure to create a matter that you can associate with a collection:
1. Navigate to the Matters tab. Collect displays a list of the active matters currently available to this
application.
2. Click New Matter.
3. Complete the fields in the Matter Details layout. See Matter Details layout fields below.
4. Click Save. Collect displays the matter details. See Viewing or editing matter details on the next
page.
You can also create a matter when you add a new collection. Click the Add link on the collection
layout. See Creating a collection on page 27.
3.1.2 Matter Details layout fields

The Matter Details layout contains the following fields:
n Name—the name of the matter.

n Number—the number you assign to the matter for reporting purposes.
n Status—the status you assign to the matter for reporting purposes. Select an existing status from the
drop-down menu or click Add to define a new one. Existing statuses include Active and Closed.
Note: Assigning a status of Closed to a matter hides it from the Active Collect view on the Collect
tab.
n Primary Contact—the name of an individual who handles communications related to the matter.
n Description—the description of the matter used for reporting purposes. Click Edit to display an
HTML text editor where you can enter the description.

3.1.3 Viewing or editing matter details
Display the matter details by clicking the name of a matter on the Matters tab. Collect also displays these
details immediately after you add a new matter. You can use the buttons at the top of the page to edit,
delete, or perform other tasks with the matter.
The details page includes the following sections:
n Matters Details—lists the name, number, status, primary contact and description of the matter.
n Collect—lists all collections associated with the matter. You can also perform the following tasks in
this section:
o Associate the matter with a new collection—to create a new collection, click New. See
Creating a collection on page 27.
o Remove a collection from Relativity—click Delete to display a pop-up window. To view
child objects and associated objects, click Dependencies.
o Modify collection details—click the Edit link for a collection. To modify the matter, click the
Edit button at the top of the page.
o Display the collection details—click the name of the collection.

4 Custodian targets
In Collect, you manage custodians that have an associated data source. The custodian target is the
combination of a custodian and data source. It is an endpoint from which RelativityOne Collect can connect
to and collect from. For example, a custodian's Google Workspace Gmail account is a custodian target.
To collect from custodians, entities either have to exist, be created, or be imported in Relativity. The
custodian and their primary email address also needs to be associated to the data source. When the
primary email address field for a custodian is present, Collect will auto-generate the required targets for
each data source while setting up a collection job.
In this document, the source is Google Workspace.
4.1 Custodians
If a custodian does not exist, you can manually create an entity from the Entities tab. Once you create an
entity in the Collect Custodian view and add it to a collect project, it becomes a custodian.
You can add custodians to Collect at different times throughout the collection process. There are different
ways to populate the entity list including using Integration Points, the RDC, or manually. For more
information, see Integration Points and RDC. To manually create a new custodian, follow the steps below:
1. Navigate to the Entities tab.

2. Click New Entity on the Custodians tab.
3. Select the Collection History layout from the drop-down menu and complete the fields. See Fields
below.
4. Click Save.
Note: When creating a custodian from Legal Hold, the Custodians - Legal Hold View is selected by
default. If Collection or Processing is also installed in the same workspace, you can view the Custodians
- Processing View or Custodians - Collection View accordingly.
4.2 Fields
The Collection Custodian layout provides the following fields:

n Custodian Type—select one of the following:
o Person—select this to enter first and last name of the individual acting as custodian of the data
you wish to process.
o Entity—select this if the custodian of the data you wish to process isn't an individual but is, for
example, just a company name. You can also select this if you wish to enter an individual's full
name without having that name include a comma once you export the data associated with it.
Selecting this changes the Custodian layout to remove the required First Name and Last Name
fields and instead presents a required Full Name field.
n First Name—the first name of the custodian. This field is only available if you've set the Custodian
Type above to Person.
n Last Name—the last name of the custodian. This field is only available if you've set the Custodian
Type above to Person.
n Full Name—the full name of the custodian of the data you wish to process. This field is only available
if you've set the Custodian Type above to Entity. When you enter the full name of an entity, that name
doesn't contain a comma when you export the data associated with it.
n Email—the email the custodian uses in the target. This email address must match the email address
within the connected data source.
4.3 Creating a custodian target

You can collect electronic data from custodians who are individuals or entities involved in a legal action or
case. You can collect electronic data for custodians from their computers, external hard drives, network
drives, and other sources. You may perform multiple collections from a single custodian. On the Custodians
tab, you can create and edit custodians as well as view their details, associate them with collections, and
perform other tasks.
Use the following procedure to create a custodian target that you can associate with a collection:
1. Enter the Name of the custodian target.

2. Click Select to select available custodians. If the custodian doesn't exist, click Add and complete
additional steps.
3. Click the Data Source drop-down menu to select a data source. For more information Collection data
sources, see Data source types and properties on page 26.
4. Enter the custodian's email address in the Target field.

4.3.1 Generating targets in the wizard
Custodian Targets can also be automatically generated in Step 4 of the Collect wizard. Click Generate
Targets to check if targets exist for the custodians you've selected for collection. If the targets do not exist,
Collect creates them based on the email address in the Entity details in each custodian. For more
information, see Collection Summary on page 40.
If an invalid custodian target is created manually, the auto-generation of custodian targets doesn't remove
the invalid custodian target. The invalid custodian target needs to be removed manually. Find out if there are
any errored targets in the Collection Summary step or on the Status Summary tab. To delete a custodian
target from the Custodians Targets tab, click the data sources checkbox and use the Delete mass
operation.
4.4 Removing custodian targets

To remove any custodian target, the custodian first needs to be removed from the collection, or collections.
You can use the Mass delete operation to delete collect custodians, also known as entities. For more
information, see the Admin Guide.
Trying to delete a custodian target before removing a custodian will result in an error.
4.5 Target status

The Target Status tab is a dashboard to see the statuses of collections. You can drill into each target from
this dashboard. Able to look into the targets by custodian, data sources, or status to find out more about
your collections. Focus on the collected components with this dashboard.
4.5.1 Reviewing collection targets

The Target Status dashboard is available after generating targets. To learn how to generate targets for a
collection, see Collect tab on page 27. Once you generate targets, the dashboard organizes by collection
jobs.
Status:
n Not started—the collection is set up, but hasn't been started.

n Started—the collection started and has not completed.
n Completed—the collection of the target completed without any errors.
n Completed with Errors—the collection of the target completed and had individual items that couldn't
be collected. For more information, see the Errors report on page 45.
n Error—the collection did not run successfully and couldn't collect from the target.

5 Google Workspace setup
Set up your Google Workspace data source with Collect by creating credentials, setting up a user account,
restricting collections, and adding the data source to Collect.
5.1 Google Workspace credentials setup

Connecting your Google Workspace to Collect takes some setup in Google and Relativity. Begin with the
credential setup in Google.
5.1.1 Creating a Google Cloud project

Create a Google Cloud project to create, enable, and use all Google Cloud services. You will use this
account to manage APIs.
To create a Google Cloud project,
1. Open the Cloud Resource Manage page, click Create Project.

2. Enter information into the fields:
n Project name—enter a memorable name for your project.

n Organization—enter the name of your organization.
n Location—enter the parent organization or folder.
3. Click Create.
5.1.2 Enable required APIs for the Project

Continuing in this process, you now need to enable the required Google Cloud Console APIs and associate
them to a new project.
To start enabling APIs,

1. In the Google Cloud Console, select the newly created project.
2. In the left-navigation menu, select API & Services > Library.
This will open up the Library page that includes all available APIs.
3. Enter Google Vault API in the search bar and search.
4. Click the Google Vault API option.
5. Click Enable.
6. In the top left corner, click the Back arrow icon.
This will take you back to the search results page with the search bar.
7. Enter Admin SDK API in the search bar and search.
8. Click the Admin SDK API option.
9. Click Enable.
10. In the top left corner, click the Back arrow icon.
This will take you back to the search results page with the search bar.
11. Enter Cloud Storage API in the search bar and search.
12. Click the Cloud Storage API option.
13. Click Enable.
Notes: This API may be enabled by default.
5.1.3 Setup OAuth2 consent screen

Follow the steps to create a OAuth2 consent screen.

1. Open https://console.cloud.google.com/ and select newly created project.
2. Click on the Navigation menu.
3. Select APIs & Services>OAuth consent screen.
4. Select Internal type.
5. Click Create.
6. Enter descriptive App name. For example, Relativity Collect.

7. Enter a User support email from within your organization.
8. Enter relativity.one as Authorized Domain.
9. Enter an email form within your organization in the Developer Contact Information field.
10. Click Save and Continue.
On the next step, you will want to add scopes.
1. Click Add or remove scopes.

2. Enter filter and select required scopes one at a time, or enter them in a text box.
The scopes are:
n https://www.googleapis.com/auth/ediscovery
n https://www.googleapis.com/auth/devstorage.read_only
n https://www.googleapis.com/auth/admin.directory.user.readonly

n https://www.googleapis.com/auth/admin.directory.group.readonly
3. Click Update.
4. Click Save and Continue.
5.1.4 Create credentials

1. Click in the top left corner.
2. Hover over APIs & Services > Credentials.
3. Click Create Credentials.
4. Click OAuth Client ID credentials.
5. Enter the following information in the fields:
n Application type—select Web application

n Name—enter a name for the credentials
n Authorized redirect URIs—enter the URI based on the RelativityOne Data Center Geo you
intend to run collections from.
RelativityOne Data Center Geo URIs
o Asia (East)—https://services.esas.relativity.one/collect-oauth-authorization/index.html
o Asia (Southeast)—https://services.seas.relativity.one/collect-oauth-
authorization/index.html
o Australia—https://services.auea.relativity.one/collect-oauth-authorization/index.html

o Brazil (South)—https://services.brso.relativity.one/collect-oauth-
o Canada (Central)—https://services.cact.relativity.one/collect-oauth-
o Europe (North)—https://services.noeu.relativity.one/collect-oauth-
o Europe (West)—https://services.wseu.relativity.one/collect-oauth-
o Germany (West Central)—https://services.dect.relativity.one/collect-oauth-
o India (Central)—https://services.inct.relativity.one/collect-oauth-
o Japan—https://services.jpes.relativity.one/collect-oauth-authorization/index.html
o Korea (Central)—https://services.krct.relativity.one/collect-oauth-
o Switzerland—https://services.chno.relativity.one/collect-oauth-
o United Arab Emirates—https://services.aeno.relativity.one/collect-oauth-
o United Kingdom (South)—https://services.ukso.relativity.one/collect-oauth-
o United States (Central)—https://services.ctus.relativity.one/collect-oauth-
o United States (East)—https://services.esus.relativity.one/collect-oauth-
6. Click Create.
After clicking Create, you will have your Client ID and Client Secret. Add them to the New Collection Source
Instance.

5.2 Google Workspace user account setup
Collections require user account on which behalf Relativity exports data. This can be a dedicated or an
existing user account.
5.2.1 Create admin role for Vault API

1. Open https://admin.google.com/ac/home.
2. Click Account>Admin roles to open the up the page.
3. Click Create New Role.
4. Enter the role name. Relativity suggests Relativity Collect.
5. Click Continue to select privileges.
6. Select the following privileges:
n Services - Google Vault > Manage Matters

n Services - Google Vault > Manage Searches

n Services - Google Vault > Manage Exports
7. Click Continue.
8. Click Create Role.
5.2.2 Create admin role for the user accounts listing

4. Enter the role name. Relativity suggests Users Reader for Collect.
5. Click Continue.
6. Select the following privileges
n Admin API privileges - Users > Read
7. Click Continue.

5.2.3 Create admin role for the groups listing
4. Enter the role name. Relativity suggests Groups Reader for Collect.
5. Click Continue.
6. Select the following privileges
n Admin API privileges - Groups > Read
7. Click Continue.
5.2.4 Enable required privileges

2. Navigate to Directory > Users to open the list of users.

3. Select or create the user you want to use.
4. Select and expand Admin roles and privileges pane.
5. Assign the following roles to the user in All organizational units scope
n Relativity Collect
n Users Reader for Collect
n Groups Reader for Collect

5.3 Restricting collections to the selected user accounts
You can restrict collections to the selected group of users by leveraging admin role scoping to
organizational units. To limit collections, you will need to create an organizational unit and add the users to
the unit. Once created, Collect will only collect data from the users within the organizational unit.
This configuration step is for Google Workspace data sources only and is optional.
5.3.1 Create an organizational unit

An organization unit restricts RelativityOne’s collections only to the selected custodians. Create an
organization unit and add selected custodians to the unit so only their information is collected.
To create an organizational unit, open Google admin Console and follow the steps below:
2. Navigate to Directory > Organizational Units.
3. On the Manage organizational units page, click the + icon.
4. In the Create new organizational unit pop-up menu, enter the Name of organizational unit.
5. (Optional) Enter description of the organizational unit.
6. Select the Parent Organization Unit (POU). If this field isn’t populated, add a POU. To create a
POU, follow the steps in Google’s documentation.
7. Click Create.

Once the organizational unit is created, the next step is to add targeted users you want to collect from to the
unit.
To add users to the organizational unit, follow the steps below:
1. Click the navigation menu.

2. Navigate to Directory > Users.
3. Select the users who should have collections restricted
4. Click Change organizational unit.
5. In the Change organizational unit pop-up menu, select appropriate organizational unit.
6. Click Continue.
7. Click Confirm.
You can upload a CSV file to bulk update users. For more information, see Google’s documentation.
5.3.2 Scope user privileges to the organizational unit

2. Navigate to Directory > Users.
3. Select or create a user account.
4. Select and expand the Admin roles a privileges pane.
5. Click the pencil icon.

6. Edit the scope of the role to the appropriate organization unit.
7. Click Save.
Groups Reader privilege can only be scoped to 'All organizational units'. This privilege is only required to
enable collections from Google Workspace Groups and it can be omitted. Doing so will disable Groups
collections on behalf of this user account.
5.4 Setting up a Google Workspace data source

There are specific steps to connect Google Workspace to Relativity when creating the data source. To set
up the Google Workspace data source, you will need to enable API access with Google Workspace and
then complete the data source settings in Relativity.
5.4.1 Creating a Google Workspace data source

After confirming that your Discover APIs are enabled, complete the set up process in Relativity.
Notes: Copy the Refresh Token value you generate in Step 10 and store it in a secure location. It can be
used to setup other Google Workspace data sources without the need to create new OAuth2 credentials.
Google Workspace allows only a single refresh token to be generated for a set of OAuth2 credentials.
To add the Google Workspace data source, follow the steps below:
1. Within the Collect application, navigate to the Collection Admin tab.
2. Click the New Collection Source Instance button.

3. Enter in a unique name for the data source.
4. Select a Google Workspace data source.
5. In the Settings pane, enter Client Id and Client Secret copied from Google’s OAuth2 credentials
page. For more information, see Creating credentials.
6. Click Generate Code.

7. Select or sign into Google’s account on which behalf collections will be performed. For more
information, see Google Workspace user account setup on page 18.
8. Click Copy Temporary Code to copy to your clipboard.
Once copied, you can close that window and return back to RelativityOne.
9. In Collect, paste the code in the Temporary Code field.
10. Click Generate Refresh Token.
The access token will be generated and populated in the Refresh Token field below.
Notes: Copy Refresh Token value and store it in a secure location. It can be used to setup other
Google Workspace data sources without the need to create new OAuth2 credentials.
Google Workspace allows only a single refresh token to be generated for a set of OAuth2
credentials.
11. Click Save.

6 Creating a collection data source
Set up workspace data sources before beginning collections. Data sources are stores of information from
which you collect data. These data sources have parameters that you can set during the creation of a
collection job.
6.1 Creating a collect data source

The Collection Admin tab is where you create, edit, and remove data sources from your workspace. Setup
only needs to be done once for each data source. You must create your data sources prior to setting up your
custodian targets. For more information, see Custodian targets on page 10.
When creating data sources, you can select different types of data sources for obtaining files. These types
include Google Workspace, Microsoft 365 (Outlook and OneDrive), Slack, and X1. In this document, you
will create a collect data source for Google Workspace.
Use the following procedure to create a new Collect source instance:
On the Collect Admin page,
1. Click the New Collection Source Instance button.

2. Enter in a unique name for the data source.
3. Select the type of data source:
n Google Workspace Chat—select to collect data from Google Chat. For more information, see
Google Chat on page 30.
n Google Workspace Drive—select to collect data from a Google Drive. For more information,
see Google Drive on page 32.
n Google Workspace Gmail—select to collect data from Google Gmail. For more information,
see Google Gmail on page 34.
n Google Workspace Groups—select to collect data from Google Groups. For more inform-
ation, see Google Groups on page 37.
4. Enter the following information in Settings:

Google Workspace OAuth2 settings

n Client Id—enter the Client ID found on the Service Account Status page in the Google Cloud
Console. For more information, see Google Workspace setup on page 13.
n Client Secret —enter the secret OAuth token copied from the Google Cloud Console user
interface.
n Refresh Token—enter the application token retrieved after generating the temporary code.
Notes: For one Client ID/Client Secret pair, you can generate just one Refresh Token – it
does not matter if you try to do it for different data source. The Refresh Token can be copied
from another data source/other location. Generating a temporary code and using it is not
necessary.
n Temporary Code—enter the code provided by Google after installing application. The Gen-
erate Code section provides steps to retrieve the Temporary Code and Access Token.
5. Click Save.
6.1.1 Data source types and properties

Each data source that can be used in Collect has different search criteria when creating a collection job. For
more information on each data source types criteria, see Criteria on page 30.

7 Collect tab
Before you begin collecting, you must create a collection job and associate it with a specific matter,
custodians, and one or more data sources. Add the custodians, data sources, and other information using
the Collect wizard. Once completed, start the collection using the Collect Console. Finally, download a
results report that details the items collected and a summary report of the entire collection job. For more
information, see Reports on page 44.
7.1 Creating a collection

Before you begin creating a collection, make sure to create a matter. For more information, see Matters on
page 8.
Use the following procedure to create a collection:
1. On the Collect tab, click the Collections sub-tab. Collect displays a list of the collections currently
added to this application.
2. Click New Collection.
3. Complete the steps in the Collect wizard. See Using the Collect wizard below
4. On the Collection Details page, click Run Collection in the console. See Collection Summary on
page 40.
7.1.1 Using the Collect wizard

The Collect wizard takes you through each step to create a collection. After completing the collection setup,
run a collection from the Collection console.
Collection wizard security permissions
A Collect user needs the following permissions to use the Collect Wizard.
n Custodian—View
When a step is complete, click Next or the hyperlink under the next step shown. Click the Previous button
to move to the previous step. Information is auto-saved when moving between steps. If any required
information is missing or incorrect, an error message displays and are prevented from moving to the next
step.
7.1.1.1 Collection Details

Complete the Collection Details step by entering information in the following fields:
n Name—the name of the collection.
Note: Enter a name using alphanumeric characters only. Special characters, such as periods,
commas, and em dashes, cannot be used and will cause an error.
n Collection Matter—the name of the matter associated with this collection. Click Edit to select an
existing matter or click Add to define a new one. See Creating a matter on page 8.
n Processing Source Location - the file repository for collected data to be stored for future pro-
cessing of documents or for storing collected data. See Processing and Collect Store on page 47.

Note: All data sources that produce RSMF have a limit of 200MB. For more information, see
Processing documentation.
n ZIP Collected Files—toggle on to compress all collected data into ZIP64 formatted containers.
Selecting Yes adds additional steps to the collect process. For more information, see Storing col-
lected data on page 42. Google data is excluded from compressing into ZIP64 formatted containers
since Google compresses the data on their end.
n Zip Password—enter a password that is required by anyone attempting to decompress the ZIP64
container files.
Note: If Processing is installed in the workspace, Collect will automatically populate the Processing
Password Bank with the password so it is available at the time the collection is processed.
n Enable Auto-Processing—toggle on to enable auto-processing. If enabled, select the workspace

and profile. All data in the in a completed collection or completed with errors collection will be pro-
cessed after collection is complete.
n Select Workspace—select a workspace within your instance to select a Processing profile to use
when creating a processing job.
n Select a Processing Profile—select a processing profile available in the drop-down menu. The
available profiles are from the selected workspace.
n Select a document prefix option—select Use Processing Profile Document Number Prefix or Use
Processing Profile Document Number Prefix to apply to each file in the processing set once it is
published to a workspace.
n Job Number—enter a number that you want assigned to the job for reporting purposes.
n Description—enter a description of the collection used for reporting purposes.
n Receive Progress Notifications—toggle on to send or receive collection job status emails. The
statuses include:
o Completed—includes completed or completed with errors job status.
o Failed—includes job status and reason for failure.

n Notification Address—enter the email address of person that wants to receive collection job
statuses.
n Data Source Type—select one or more data sources to use in the collection. For more information,
see Data source types and properties on page 26.
Note: Google limits simultaneous exports through their Vault API to 20 exports across organizations.
Collect generates one export for each custodian mailbox or Drive repository. If you attempt to collect more
than 20 mailboxes, or your organization attempts to use the Google Vault API for more than 20 exports at
once, you will encounter errors depending on the timing of the mailbox exports.

7.1.1.2 Custodians
Complete the Custodians step by assigning custodians to the project. Follow the steps below to assign a
custodian:
1. From the Unselected custodians table, use the column filters to locate custodians.
2. Click a check box next to a custodian.
Notes: If you select multiple Slack custodians in the same collection, the channels they share will
only collect once.
3. Click to add select custodians. Click to add all custodians.

4. Click Next.

Note: There is a limit of 10,000 custodians with targets in the custodian picker.
7.1.1.3 Configure Data Source

Configure the data sources chosen in the Collection Details step. If you select multiple data sources in the
first step, you'll configure all sources in the step. Switch between each source by clicking the name of the
data source in the left navigation menu. Clicking Next and Previous also moves you through the data
sources. Select individual data sources by clicking on the checkbox and then using the right arrows to select
them. After selecting the data sources to configure, fill out the criteria. Each data source has different criteria
to enter.
Data source criteria

Add criteria to collect specific data. To configure the data sources, complete the following fields:
n Select and unselected tabs—choose the data sources to collect from by moving unselected data
sources to the selected list.
n Field—choose the field to filter on within the data source.
Notes: This field is only required when a calendar source is selected.
n Operator—choose an operator such as equals, contains, greater than, or less than.

n Value—enter a value to find in the selected field.
After selecting field options, you must click Add Criteria. Add multiple criteria to search data sources.
Things to know about criteria:
n Each criteria is then separated by an AND operator.

n Leave the data source criteria empty to collect all data from the sources.
Criteria
Filter a data source's data that you want to collect by adding criteria. This section covers the different criteria
for each data source. It also includes what can be searched within each data source. The criteria options
change based on the selected data source.
Google Chat
The following table lists the filter criteria support for Google Workspace Chat collections. Google Workspace
Chat data is collected in RSMF.
Setting criteria for Google Workspace Chat is not required. For more information on Advanced examples,
see Google Workspace documentation.
Criteria Operators Description Example

Advanced Equals When you use the Advanced property in For more inform-
a query, specific Google Workspace ation on
search criteria become available in Col- Advanced
lect. For more information, see Google examples, see
Workspace documentation. Google Work-
space doc-
umentation.

Content Type Equals When you used the Content Type prop- If you search with
erty in a query, the search returns mes- the value set to
sages with specific file types. Google Docs,
your results
include all Google
Docs sent as mes-
sages.
Keyword Search Equals When you use the Keyword Search If you search
property in a query, the search returns “Dear John,” your
all messages that contain the text you’re results include all
searching for. For more information, see messages that
Criteria on the previous page. contain the text in
email body. Note
that this is not the
same as search-
ing for “Dear” OR
“John”. In order to
do that you need
to enter keywords
in separate lines.
Message Source Equals When you use the Message Source If you search with
property in a query, the search returns the value set to
all direct messages or all messages in "Messages in
rooms. Rooms," your res-
ults include only
messages sent in
a group chat and
no direct mes-
sages will be
included.
Sent/Updated Greater Than or Equals, When you use the Sent/Updated prop- If you search
Date Less Than, Less Than erty in a query, the search returns all “Greater Than
or Equals messages that equal/doesn’t equal, 1/1/2001,” your
greater/less than the date entered. results include all
messages sent
after January 1,
2001.
Slice Interval in Equals When you use The Slice Interval in If you search with
Hours Hours property, the search returns all a slice interval set
messages in a specific time range or to one hour and a
defaults the slice interval to 24 hours. conversation
spans five hours,
you will end up
with five RSMFs

after processing.
User At Contains When you use the User At property in a If you search
query, the search returns all messages “UserExample1”
that contain the text in the User At field. your results
include all mes-
sages sent to
people with the
UserExample1 in
their email
address.
User From Contains When you use the User From property If you search
in a query, the search returns all mes- “ExampleUser1,”
sages that contain the text in the User your results
From field. include all mes-
sages sent by
people with the
UserExample1 in
their email
address.
Included in the Google Workspace Chat Criteria are two toggles:
n Include results from Rooms—enable this toggle to include all messages in rooms, along with direct
messages, that match your query. Disable to collect only direct messages that match your query.
n Disable RSMF conversion—enable this toggle to keep data in its original format by preventing
Relativity from converting the files into Relativity's short message format (RSMF) files.
Google Drive
The following table lists the filter criteria support for Google Workspace Drive collections. Setting criteria for
Google Workspace Drive is not required. For more information on Advanced examples, see Google
Workspace documentation.

Advanced Equals When you use the Advanced property in For more inform-
a query, specific Google Workspace ation on
search criteria become available in Col- Advanced
lect. For more information, see Google examples, see
Workspace documentation. Google Work-
space doc-
umentation.
File Type Equals When you use the File Type property in If you select
a query, the search returns all files that "Google Sheets"
equals what is entered. as your value,
your results
include Google

Sheet files.
Filename Contains When you use the Filename property in If you search
a query, the search returns all files that "Important_Docu-
contain the value entered. ment,” your res-
ults include all
files with "Import-
ant_Document” in
the filename.
Keyword Search Search In When you use the Keyword Search If you search
property in a query, the search returns “Dear John,” your
all files that contain the text you’re results include all
searching for. For more information, see messages that
Criteria on page 30. contain the text in
the file. Note that
this is not the
same as search-
ing for “Dear” OR
“John”. In order to
do that you need
to enter keywords
in separate lines.
Modification Date Equals, Does Not Equal, When you use the Modification Date If you search
Greater Than, Greater property in a query, the search returns “Less Than
Than or Equals, Less all files that equal/doesn’t equal, great- 1/1/2021,” your
Than, Less Than or er/less than the selected date. results include all
Equals files received
before January 1,
2021.
Owner Contains When you use the Owner property in a If you search
query, the search returns all messages “Iscovery,” your
that contain the text in the Owner field. results include all
files sent by
people with the
"Iscovery" in their
name, such as
"Ed Iscovery."

Shared By Contains When you use the If you search
Shared By property in a query, the “ExampleUser1,”
search returns all files that contain the your results
text in the Shared By field. include all filed
shared by people
with the User-
Example1 in their
name.
Shared With Contains When you use the Shared With property If you search
in a query, the search returns all files “UserExample1,”
that contain the text in the Shared With your results
field. include all files
shared with
people with the
UserExample1 in
their name.
Version Date Equals When you use the Version Date prop- If you search
erty in a query, the search returns the 1/1/2021, your res-
version of files on the selected date. ults include only
the version of the
files on 1/1/2021.
The results won't
include earlier or
later versions of
the file.
Included in the Google Workspace Drive Criteria is one toggle:
n Collect files from shared drives—enable the toggle to retrieve data from shared drives, along with
personal drives, that match the criteria. Disable to collect only data from personal drives that match
the criteria.
Google Gmail
The following table lists the filter criteria support for Google Workspace Gmail collections. Setting criteria for
Google Workspace Gmail is not required. For more information on Advanced examples, see Google

Advanced Equals When you use the Advanced property For more inform-
in a query, specific Google Workspace ation on Advanced
search criteria become available in Col- examples, see
lect. For more information, see Google Google Workspace
Workspace documentation. documentation.
Email BCC Contains When you use the Email From property If you search
in a query, the search returns all mes- “@example.com,”
sages that contain the text in the Email

BCC field. your results include
all blind carbon
copied messages
received by people
with the
@example.com in
their email
address.
Email CC Contains When you use the Email From property If you search
sages that contain the text in the Email your results include
CC field. all carbon copied
messages
received by people
with the
@example.com in
their email
address.
Email From Contains When you use the Email From property If you search
From field. all messages sent
by people with the
@example.com in
their email
address.
Email Received Equals, Does Not When you use the Email Received Date If you search “Less
Date Equal, Greater Than, property in a query, the search returns Than 1/1/2021,”
Greater Than or Equals, all messages that equal/doesn’t equal, your results include
Less Than, Less Than greater/less than the date entered. all emails received
or Equals before January 1,
2021.
Email Sent Date Equals, Does Not When you use the Email Sent Date If you search
Equal, Greater Than, property in a query, the search returns “Greater Than
Greater Than or Equals, all messages that equal/doesn’t equal, 1/1/2001,” your res-
Less Than, Less Than greater/less than the date entered. ults include all
or Equals emails sent after
January 1, 2001.

Email To Contains When you use the Email To property in If you search
a query, the search returns all mes- “@example.com,”
To field. all messages sent
to people with the
@example.com in
their email
address.
Has Attachments Equals, Does Not Equal When you use the Has Attachments If you mark toggle
property, the search returns emails with the Value setting
or without attachments based on the On, your results
Value setting. include all mes-
sages that include
an attachment.
Is Draft Equals Indicates whether or not messages are If you mark toggle
written and not sent. Use the values the Value setting
true or false. On, your results
include all emails
that are in the draf-
ted state.
Keyword Search Search In When you use the Keyword Search If you search “Dear
property in a query, the search returns John,” your results
all messages that contain the text include all mes-
you’re searching for. For more inform- sages that contain
ation, see Criteria on page 30. the text in email
body. Note that this
is not the same as
searching for
“Dear” OR “John”.
In order to do that
you need to enter
keywords in sep-
arate lines.
Label Equals When you use the Label property, the If you search
search returns all messages that con- "Important," your
tains the search word or phrase in the results include all
emails' label. emails that are
marked with the
"Important" label.
Subject Contains When you use the Subject property, the If you use the Sub-
search returns all messages that con- ject property in a
tains the search word or phrase in the query, the search
email's title.

returns all mes-
sages which the
subject line con-
tains the text you’re
searching for. In
other words, the
query doesn’t
return only those
messages that
have an exact
match. For
example, if you
search for subject
“Quarterly Fin-
ancials,” your res-
ults include
messages with the
subject “Quarterly
Financials 2018.”
Included in the Google Workspace Gmail Criteria is one toggle:
n Collect all emails with attachments regardless of criteria—enable the toggle to collect emails
and attachments. Disable to collect only emails that match the criteria.
Google Groups
The following table lists the filter criteria support for Google Workspace Groups collections. Setting criteria
for Google Workspace Groups is not required. For more information on Advanced examples, see Google

Advanced Equals When you use the Advanced property For more inform-
in a query, specific Google Workspace ation on Advanced
search criteria become available in Col- examples, see
lect. For more information, see Google Google Workspace
Workspace documentation. documentation.
Email BCC Contains When you use the Email From property If you search
BCC field. all blind carbon
copied messages
received by people
with the
@example.com in
their email
address.

Email CC Contains When you use the Email From property If you search
CC field. all carbon copied
messages
received by people
with the
@example.com in
their email
address.
Email From Contains When you use the Email From property If you search
From field. all messages sent
by people with the
@example.com in
their email
address.
Email Received Equals, Does Not When you use the Email Received Date If you search “Less
Date Equal, Greater Than, property in a query, the search returns Than 1/1/2021,”
Greater Than or Equals, all messages that equal/doesn’t equal, your results include
Less Than, Less Than greater/less than the date entered. all emails received
or Equals before January 1,
2021.
Email Sent Date Equals, Does Not When you use the Email Sent Date If you search
Equal, Greater Than, property in a query, the search returns “Greater Than
Greater Than or Equals, all messages that equal/doesn’t equal, 1/1/2001,” your res-
Less Than, Less Than greater/less than the date entered. ults include all
or Equals emails sent after
January 1, 2001.
Email To Contains When you use the Email To property in If you search
a query, the search returns all mes- “@example.com,”
To field. all messages sent
to people with the
@example.com in
their email
address.
Has Attachments Equals, Does Not Equal When you use the Has Attachments If you mark toggle
property, the search returns emails with the Value setting
or without attachments based on the On, your results
Value setting. include all mes-
sages that include

an attachment.
Is Draft Equals Indicates whether or not messages are If you mark toggle
written and not sent. Use the values the Value setting
true or false. On, your results
include all emails
that are in the draf-
ted state.
Keyword Search Search In When you use the Keyword Search If you search “Dear
property in a query, the search returns John,” your results
all messages that contain the text include all mes-
you’re searching for. For more inform- sages that contain
ation, see Criteria on page 30. the text in email
body. Note that this
is not the same as
searching for
“Dear” OR “John”.
In order to do that
you need to enter
keywords in sep-
arate lines.
Label Equals When you use the Label property, the If you search
search returns all messages that con- "Important," your
tains the search word or phrase in the results include all
emails' label. emails that are
marked with the
"Important" label.
Subject Contains When you use the Subject property, the If you use the Sub-
search returns all messages that con- ject property in a
tains the search word or phrase in the query, the search
email's title. returns all mes-
sages which the
subject line con-
tains the text you’re
searching for. In
other words, the
query doesn’t
return only those
messages that
have an exact
match. For
example, if you
search for subject
“Quarterly Fin-

ancials,” your res-
ults include mes-
sages with the
subject “Quarterly
Financials 2018.”
Included in the Google Workspace Groups Criteria is one toggle:
n Collect all emails with attachments regardless of criteria—enable the toggle to collect emails
and attachments. Disable to collect only emails that match the criteria.
7.1.1.4 Collection Summary

Complete the creation of the collection by reviewing all steps, custodians, data sources, and targets, before
finalizing. If Google Workspace custodian targets weren't created before started the project, click Generate
Targets. Clicking Generate Targets will check to see if targets exist for the custodians you have selected for
collection. If the targets do not exist, Collect will automatically create them based on the email address
contained in the Entity record for each custodian.
Generate the targets to retrieve all known Collect targets based on the custodians and data sources
selected. These data sources include Google Workspace.
Click the Generate Targets button to ensure you are using the latest target set. Clicking Generate Targets
will check to see if targets exist for the custodians you've selected for collection. If the targets weren't
created manually, Collect will automatically create them based on the email address contained in the Entity
record for each custodian. The targets will automatically generate when reaching the Summary Step of the
Collect Wizard, but the console button prevents returning to the Collect Wizard.
In the Targets section, you will see a number next a custodian's name. The number listed is the number of
custodian targets found in the associated data source. A zero means Collect did not find any custodian
targets with that email address in that data source. A one means Collect found a single custodian target
associated with the email address within the data source. Any number greater than one means that Collect
found multiple custodian targets with that email address within the data source.
If there is no color highlighting the number, it means Collect already found and generated the custodian
target. If there is a green highlight, Collect auto-generated the custodian target. If there is a red highlight,
Collect could not auto-generated this custodian target. If red, you can still manually generate the custodian
target. For more information, see Creating a custodian target on page 11.

Complete the collection setup by clicking View Collection Details. Once you finish creating the collection,
it redirects you to the Collection Details page. From the Collection Details page, you can run the collection
from the Collection Summary on the previous page.
7.2 Viewing or editing collection details

You can display the collection details by clicking the name of a collection on the Collections tab. Collection
also displays these details immediately after you add a new collection. On the Collection Details page, the
buttons at the top of the page to edit, delete, or perform other collection tasks. Editing a collection takes you
to the first step in the wizard. For more information, see Using the Collect wizard on page 27.
Note: Once a collection has started, the collection can't be edited and is locked in read-only mode.
n Collection Details—lists the information that you entered or selected when you created the col-
lection:
o Name—lists the name given to the collection.
o Collection Matter—lists the matter used in the collection.
o Job Number—lists a number assigned to the job for reporting purposes.
o Description—lists a description of the collection used for reporting purposes.
o Processing Source Location—lists the file repository that collected data is stored for future
processing of documents or for storing collected data.
o Auto Processing Workspace—lists if you toggled the field on or off.
o Auto Processing Profile—lists the processing profile if you toggled the Auto Processing Pro-
file field on.
o Auto Processing Document Numbering Prefix Option—lists the prefix option if you selec-
ted one.
o Job Status—the status of the collection (New, Not Started, Started, Completed, Error, Com-
pleted with Errors).
o Error Message—lists a message if collection job did not complete due to errors.
o Zip Collected Files—lists if you selected to zip collected files.
o Zip Password—lists the password that is required by anyone attempting to decompress the
ZIP64 container files.
o Receive Email Notifications—lists if you toggled on to send or receive collection job status
emails.
o Notification Address—lists the email address of the person that will receive collection job
statuses.
n Collection Console—displays buttons that you can use to perform the following tasks. See Collect
console on page 43.

n Data Sources—lists all the collection activities associated with this collection.
o Custodian—the custodian associated with the collection.
o Source Instance—the name of the data source associated with the collection.
o Data Type Name—the name of the target associated with the collection.
o Status—displays one of the following statuses:
l Not Started—the collection has not been started.
l Started—the collection is in progress.
l Completed—the collection is done.
l Completed with Errors—the collection of the target completed and one or more tar-
gets had errors. For more information, see the Errors report on page 45.
l Error—the collection failed. For more information, see Collect reports on page 45.
o Error—lists the error message if the status is Failed.
o Collected Items—the number of files collected from the target without error. If nothing is col-
lected, a 0 is listed.
o Collected Item Total—the number of files that there are to collect without errors. If nothing is
collected, a 0 is listed.
o Target—the custodian target associated with the data source.
o Result Link—a Comma Separated Values file download listing all individual items collected
from the target. It contains all of the associated metadata for each collected item as well. If no
results, the file is empty. For more information, see Collect tab on page 27.
Notes: Google Workspace results download as a .xml file that can be converted into a .csv
file using a third-party tool.
o Error Link—a Comma Separated Values file download listing any individual items that
couldn't be collected because of errors during the collection. The report provides as much
metadata as it can along with as much error information as we can get from the source to help
identify what caused the error. If no errors, the file is empty. For more information on errors,
see Collect tab on page 27.
Notes: Google Workspace results download as a .xml file that can be converted into a .csv
file using a third-party tool.
7.2.1 Storing collected data

Selecting Yes on the Collect Files in ZIP field, your collected data will be containerized and put into a
password protected compressed folder. The compressed folders separated by the custodian target
collected. Each custodian target collect has its own folder. These folders will split when reaching a set size.
The compressed folders are then stored in the processing staging area by default.
These compressed folders can be secured with a password. You can enter a password that you or another
user needs to enter to open the compressed folder. These passwords are stored in the password bank and
can be retrieved there at a later time.

To export your collected data, use the RelativityOne Staging Explorer.
7.2.2 Viewing collected data

When Relativity collects the data, Relativity accepts the path names and file names that the source
provides. On occasion, the collection source modifies the path name or file name.
7.2.2.1 Group and individual collections

To view grouped collections data (Bloomberg Chat, Google Chat, Slack, Teams), click the Get Results link
to view your collection data. Although the Data Sources table will show N/A in the Collected Items and
Collected Item Total columns, the collected data is still available in the download. These columns show N/A
because more than one set of custodian data is included in the collection.
7.3 Collect console

After completing a setup, run the collection with the collection console. Verify connection, start or stop a
collection, and view a collection report from the Collection console on the Collection Details page.
7.3.1 Start Collection

Click the Start Collection button the initiate the collect project.
7.3.2 Stop Collection

Click Stop Collection to end the collection project that is currently running. Once this button is clicked, a
warning pop-up message appears to confirm that you want to stop. If the collection is stopped, the collection
cannot be restarted.
7.3.3 Retry Collection

The Retry Collection button is only available when a collect job doesn't complete because of errors. Click
Retry Connection to start another collect job that only retries the targets that have failed. Targets that
completed successfully won't be retried.
7.3.4 Create Processing Job

Click Create Processing Job to create a processing set from the collected documents from the data
sources. Locate these documents in the Processing Source Location set in Collection Details.
When you click the Create Processing Job button, a pop-up window displays with two fields:

n Select a workspace—select a workspace within your instance to select a Processing profile to use
when creating a processing job.
n Select a Processing Profile—select a processing profile available in the drop-down menu. The
available profiles are from the selected workspace.
n Select a Document Numbering Prefix Option—select Use Processing Profile Document Number
Prefix or Use Processing Profile Document Number Prefix to apply to each file in the processing set
once it is published to a workspace.
n Clone Profile—toggle off to use the selected processing profile or toggle on to clone the selected
processing profile and use the clone profile in conjunction with the processing set that is created.
After selecting a processing profile and deciding on cloning the profile, click the Submit Collection button.
Once the collection is submitted, Relativity creates a Processing Set with the same name as the collection
job. The Processing Set includes all data that was collected in the collection job.
7.3.5 Clone Collection

Click the Clone Collection button to duplicate the open collect job. Any collect job that has a status other
than New can be cloned.
After clicking the Clone Collection button, a pop-up modal displays the progress and completion of the
clone.
Once the job is cloned, it is placed in the Not Started status and can be found in the Collections list under the
same name with "Cloned - YYYY-MM-DD HH.MM.SS" attached to the end. All collection totals for the
cloned job associated targets are reset to zero. The Collection Detail Custodian Target fields are reset to 0.
The cloned collect job will also generate the new targets.
7.3.6 Reports
Collect includes comprehensive reporting capabilities that you can use to view information about your
collections. You can generate these reports in the collection console within a collection project. Click on the
name of a report to download. When generating a report, Relativity downloads different files through your
browser. For more information on specific reports, see Collect reports on the next page.

8 Collect reports
Collect offers comprehensive reporting capabilities that you can use to view information about collections.
You can set options to generate these reports based on matter and collection as well as other combinations.
Note: If you've developed and used a new data source plugin using the Collection API, the Targeted
Collection Activity Report reports on the new data source or sources accordingly.
8.1 Running reports

You can generate these reports in the collection console within a collection project. Click on the name of a
report to download. Locate the Collection Summary and Collection Details report in the collection console.
Locate the Results and Error report in the Data Sources table on the Collection Details page.
When generating a report, Relativity downloads different files through your browser.
8.1.1 Collection Summary report

The Collection Summary report includes the target, target status, number of items collected, and the
collection size. The report is grouped by custodians. Grouping by custodians makes it easy to sort the
targets for each custodian with subtotals for each custodian. Grand totals are at the end of the report. The
report downloads as a PDF file.
This report also includes filters that were used at any point in the collection. For example, if a modification
data that is great or equals to 1/1/2010 is added at the _____ criteria level, then that filter is listed below the
summary report table.
8.1.2 Collection Details report

The Collection Details report includes two files: the first file includes the successfully collected results of all
items and their metadata. The second file includes the errored collection data. The error file includes as
many of the items and as much of the items' metadata as it can. The report downloads as a CSV file.
This report, both files, is also stored in the assigned Azure AD file share. It is included in the collection
output.
8.1.3 Results report

The Results report is an XML file download of the results collected from the target. If no results, the file is
empty.
The Results report link for each target downloads as an XML file that contains a list of all individual items
collected. These items include emails, files, or etc. It contains all of the associated metadata for each item. If
no items were collected the file is empty.
8.1.4 Errors report

A Comma Separated Values file download of the errors that occurred during the collection from the target. If
no errors occurred, the file is empty.
If the application is reporting errors with requests, creating objects, or parsing, check for correct
permissions, check for healthy connections, and check if the fileshare is working. If the setup is correct, start
diagnosing errors.

8.1.4.1 Errors.csv
The report file lists one error per line. Each item is listed with an error ID alongside the message of the error
that caused the item failure. Per-item errors only occur in the download phase of the collection; if an error
occurs before (for example, if data is unavailable during our check) or after (for example, the worker cannot
write the results.csv file to the fileshare) then there will be no record in the errors.csv report.

9 Collect Store
Large volumes of raw collected evidence can be stored in the RelativityOne Store instead of being
processed right away. Migrating collected data to storage before processing or review reduces consumption
of physical space and reduces RelativityOne resources during an upgrade. From RelativityOne Store, you
can process or start reviewing the data at a more suitable time. For more information, see Store on
the RelativityOne documentation site.
When wanting to store collected data, select the Store option as the processing source location as the
collection output in the Collect Details step of the Collect wizard. For more information, see Using the
Collect wizard on page 27.
9.1 Moving collected data into storage

When creating a collection job, you have to select a Processing Source Location. The Store option is
available in the Processing Source Location drop-down menu within the first step of the Collect Wizard. For
more information on the Processing Source Location, see Using the Collect wizard on page 27.
9.2 Exporting collected data

When it's necessary to export the data, the user needs to use the RelativityOne Staging Explorer to export
the collected data located in Store. For more information, see RelativityOne Staging Explorer on the
RelativityOne documentation site.
Before using the RelativityOne Staging Explorer, the data can be containerized in a compressed folder if
option is selected so the metadata of the collection doesn't change when it is exported.

10 Monitor
Monitor pending, running, and completed collect jobs in the Monitor tab. The Monitor page only tracks
collect jobs from the last 24 hour time range.
The queued column lists the created collect jobs that haven't started. The running column lists collect jobs in
progress and with their current progress displayed in a status bar. The completed column lists collect jobs
completed successfully, completed with errors, the amount of data collected, and the elapsed time.

Proprietary Rights
This documentation (“Documentation”) and the software to which it relates (“Software”) belongs to
Relativity ODA LLC and/or Relativity’s third party software vendors. Relativity grants written license
agreements which contain restrictions. All parties accessing the Documentation or Software must: respect
proprietary rights of Relativity and third parties; comply with your organization’s license agreement,
including but not limited to license restrictions on use, copying, modifications, reverse engineering, and
derivative products; and refrain from any misuse or misappropriation of this Documentation or Software in
whole or in part. The Software and Documentation is protected by the Copyright Act of 1976, as amended,
and the Software code is protected by the Illinois Trade Secrets Act. Violations can involve substantial
civil liabilities, exemplary damages, and criminal penalties, including fines and possible imprisonment.
©2023. Relativity ODA LLC. All rights reserved. Relativity® is a registered trademark of Relativity
ODA LLC.

11 Index
C
Collect 27
Collect wizard 27

2RelativityOne - Collect - Google Workspace

Uploaded by

Copyright:

Available Formats

2RelativityOne - Collect - Google Workspace

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2RelativityOne - Collect - Google Workspace

Uploaded by

Copyright:

Available Formats

Relativity Collect - Google

Relativity Collect - Google Workspace 2

Relativity Collect - Google Workspace 3

Note: This document covers the Google Workspace source.

Relativity Collect - Google Workspace 4

2.1 System requirements for Collect

2.2 Installing Collect

n Analytics server setup

2.2.1 Installing Collect from the Application Library to a workspace

Relativity Collect - Google Workspace 5

5. Click in the Choose from Application Library field.

2.3 Permissions to run Collect

Relativity Collect - Google Workspace 6

n Collection – View, Edit, Add n Entities n None

n Collection Detail Request – View, Edit, Add

n Collection Detail Source Instance – View,

Relativity Collect - Google Workspace 7

3.1.1 Creating a matter

3.1.2 Matter Details layout fields

n Name—the name of the matter.

Relativity Collect - Google Workspace 8

Relativity Collect - Google Workspace 9

1. Navigate to the Entities tab.

Relativity Collect - Google Workspace 10

4.3 Creating a custodian target

1. Enter the Name of the custodian target.

Relativity Collect - Google Workspace 11

4.4 Removing custodian targets

4.5 Target status

4.5.1 Reviewing collection targets

n Not started—the collection is set up, but hasn't been started.

Relativity Collect - Google Workspace 12

5.1 Google Workspace credentials setup

5.1.1 Creating a Google Cloud project

1. Open the Cloud Resource Manage page, click Create Project.

n Project name—enter a memorable name for your project.

5.1.2 Enable required APIs for the Project

Relativity Collect - Google Workspace 13

Notes: This API may be enabled by default.

5.1.3 Setup OAuth2 consent screen

Relativity Collect - Google Workspace 14

6. Enter descriptive App name. For example, Relativity Collect.

1. Click Add or remove scopes.

Relativity Collect - Google Workspace 15

5.1.4 Create credentials

n Application type—select Web application

Relativity Collect - Google Workspace 16

Relativity Collect - Google Workspace 17

5.2.1 Create admin role for Vault API

n Services - Google Vault > Manage Matters

Relativity Collect - Google Workspace 18

5.2.2 Create admin role for the user accounts listing

n Admin API privileges - Users > Read

Relativity Collect - Google Workspace 19

n Admin API privileges - Groups > Read

5.2.4 Enable required privileges

2. Navigate to Directory > Users to open the list of users.

Relativity Collect - Google Workspace 20

5.3.1 Create an organizational unit

Relativity Collect - Google Workspace 21