RCA Practice Questions

The Imaging Warnings tab specifically logs non-critical issues that occur during an imaging job which may affect the quality or completeness of the generated image. A common warning is for MSG or EML files where the body of the email is exceptionally long. The imaging engine may truncate the content to fit on the page, and Relativity logs a warning to alert the user that the resulting image might not contain the full, original text.

A. Embedded images not processing is typically a processing error, not an imaging warning.

B. Password-protected files are identified during the processing stage and logged in the Processing Errors tab, as they cannot be opened to be imaged.

D. Non-imageable content is a broad category; files that cannot be imaged at all (e.g., binaries) would fail, not just generate a warning.

1. Relativity. (n.d.). Imaging native files. Relativity Documentation. Retrieved from https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Imagingnativefiles.htm. (This section states, "Relativity generates a warning when it encounters a long email message (MSG or EML) that may have its content cut off in the generated image.")

2. Relativity. (n.d.). Viewing imaging job details. Relativity Documentation. Retrieved from https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Imagingjobsandqueues.htm#Viewing. (This page describes the function of the Imaging Warnings tab.)

The RelativityOne Staging Explorer (ROSE) is a client-side application specifically designed for high-speed, bulk data transfers to and from the RelativityOne cloud environment. It leverages Aspera's FASP protocol to maximize transfer speed and reliability, making it the designated tool for moving large data volumes, such as exports or productions, from RelativityOne storage to a local computer. Simple file downloads are not practical for large-scale transfers, and Integration Points serves a different purpose.

A. Simple File Download is a browser-based function suitable for single files or very small batches, not for rapid, large-scale data transfer.

B. File Transfer Protocol (FTP) is a generic protocol; ROSE uses the proprietary Aspera protocol, which is much faster and more reliable for WAN transfers.

C. Relativity Integration Points (RIP) is used for transferring structured data and documents between workspaces or between Relativity and other systems, not for bulk file downloads to a local machine.

1. Relativity. (2023). RelativityOne Staging Explorer. RelativityOne Documentation. Retrieved from https://help.relativity.com/RelativityOne/Content/RelativityOne/StagingExplorer/RelativityOneStagingExplorer.htm. The document states, "The RelativityOne Staging Explorer is a utility that allows you to upload and download files to and from your RelativityOne staging area." It highlights its use for "large data sets."

2. Relativity. (2023). Exporting with the RelativityOne Staging Explorer. RelativityOne Documentation. Retrieved from https://help.relativity.com/RelativityOne/Content/RelativityOne/StagingExplorer/ExportingwiththeRelativityOneStagingExplorer.htm. This page details the specific workflow for "downloading large document sets from RelativityOne to a local computer."

RelativityOne is the cloud-based, Software-as-a-Service (SaaS) version of the Relativity platform. It provides a comprehensive suite of tools for eDiscovery, including processing, review, analytics, and production, all hosted within a secure cloud environment (Microsoft Azure). This model eliminates the need for local hardware and infrastructure management, offering scalability and accessibility. It is designed to manage the entire eDiscovery lifecycle from data collection to presentation.

A. RelativityOne is a cloud platform, the opposite of local storage. It is designed to remove the need for on-premises hardware.

C. While Relativity utilizes a robust SQL database, calling it just a "database tool" is a significant understatement of its full eDiscovery platform capabilities.

D. Relativity includes advanced search functionalities, but it is a complete eDiscovery solution, not solely a search engine.

1. Relativity. (n.d.). RelativityOne. Relativity Documentation. Retrieved from https://help.relativity.com/RelativityOne/Content/Home.htm (See "Welcome to RelativityOne" section, which describes it as "a secure and easy-to-run cloud e-discovery platform.")

2. Relativity. (n.d.). What is RelativityOne? Relativity Website. Retrieved from https://www.relativity.com/products/relativityone/ (Describes RelativityOne as "The leading e-discovery SaaS platform.")

A scheduled run refers to a process configured to execute automatically at a specific time or on a recurring schedule. This automation eliminates the need for manual intervention for repetitive tasks. In Relativity, features like Structured Analytics sets, imaging jobs, and processing can be configured to run on a schedule, ensuring tasks are performed consistently without direct user action at the time of execution.

A. Manual process: This is the opposite of a scheduled run, which is defined by its automation and lack of manual initiation for each execution.

C. Search query: A search query is a set of criteria to find documents; it can be part of a scheduled process but is not the process itself.

D. Export process: An export can be scheduled, but "scheduled run" is a general term for any automated job, not just exports.

1. Relativity Documentation. (n.d.). Structured Analytics. Relativity Server 2023 Documentation. Retrieved from https://help.relativity.com/RelativityOne/Content/Relativity/StructuredAnalytics/Structuredanalytics.htm. (See section on "Running structured analytics" which describes scheduling options).

2. Relativity Documentation. (n.d.). Imaging Sets. Relativity Server 2023 Documentation. Retrieved from https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Imagingsets.htm. (See section on "Scheduling an imaging job").

Pivot charts are a core data visualization tool in Relativity. They allow users to graphically summarize data from document fields in the form of bar charts, pie charts, or line charts. This visual representation helps in quickly identifying patterns, trends, and distributions within a dataset. For example, a user could create a pivot chart to see the number of documents per custodian or the distribution of documents over time, which is essential for case assessment and review management.

A. Editing documents is performed in the document viewer, not through pivot charts, which are for data aggregation.

C. Importing data is handled by specific tools like the Relativity Desktop Client (RDC) or Integration Points.

D. Running OCR is a separate process for extracting text from images and is not related to pivot functionality.

1. Relativity. (n.d.). Pivot. Relativity Documentation. Retrieved from https://help.relativity.com/RelativityOne/Content/Relativity/PivotandDashboards/Pivot.htm. (The documentation states, "With Pivot, you can create a chart or grid to visually represent the data in a workspace.")

2. Relativity. (n.d.). Dashboards. Relativity Documentation. Retrieved from https://help.relativity.com/RelativityOne/Content/Relativity/PivotandDashboards/Dashboards.htm. (This page explains how dashboards use widgets, including Pivot charts, to "visualize the data in your workspace.")

In Relativity, a "Choice" is the object used to store the specific, predefined values for single-choice and multiple-choice fields. For example, a "Responsiveness" field would have choices like "Responsive" and "Not Responsive." These choices are created and managed as separate objects within a workspace. When a user codes a document, they are selecting one of these choice objects, and a link between the document and the selected choice is stored in the database. Layouts display these choices, but the choices themselves are the underlying objects.

B. Layouts are the web forms or user interfaces where coding fields and their available choices are displayed for user interaction.

C. Views are customizable lists that determine which fields (columns) are shown for a set of documents, not the storage for coding values.

D. Indexes (e.g., dtSearch, Analytics) are data structures that make document content and metadata searchable; they do not store the primary coding values.

Relativity Documentation, "Fields, choices, and layouts," Version: RelativityOne. This page states, "Choices are the predetermined values that are applied to single and multiple choice list fields."

Relativity Documentation, "Relativity objects," Version: RelativityOne. The documentation lists "Choice" as a distinct workspace object, defining it as a value for a single or multiple choice field.

The Group Identifier field is a relational field type specifically designed in Relativity to connect groups of related documents. This is most commonly used to maintain family relationships, such as linking an email to all of its attachments. When documents are processed, a common identifier is populated in this field for all members of a family group, allowing users to easily view and manage them together. This functionality is crucial for maintaining the context and integrity of document sets during review.

A. Fixed length text: This field type stores a specific number of characters and is not designed to create relational links between documents.

C. Whole number: This field stores integer values and lacks the inherent relational properties needed to group document families.

D. Date: This field is used exclusively for storing date and time information and cannot be used to group related documents.

- Relativity. (2023). Fields. Relativity Documentation. Retrieved from the Relativity Community portal. In the section "Field types," the Group Identifier is described as the field that "identifies a group of related documents, such as an email conversation, or an email with its attachments."

- Relativity. (2023). Adding and editing fields. Relativity Documentation. Retrieved from the Relativity Community portal. The section on "Relational Fields" details how the Group Identifier links family documents.

Fuzzy searching is a feature of dtSearch that finds documents containing terms similar in spelling to the specified term. It is useful for identifying misspellings, typographical errors, or variations in character recognition (OCR) within a document set. The degree of similarity is controlled by the fuzziness level, which determines the number of character differences allowed between the search term and the matched term. For example, a search for "apple~1" could return documents containing "apply" or "axple".

A. Exact matches only: This describes a standard keyword search, which is the opposite of fuzzy searching's purpose of finding variations.

C. Delete duplicates: This function is handled by deduplication processes, which identify and remove exact or near-duplicate files, not by a search methodology.

D. Sort documents: Sorting is an organizational function based on metadata fields like date or author, and is unrelated to finding conceptually similar terms.

- Relativity - Searching. (n.d.). dtSearch operators. Relativity Documentation. Retrieved from the RelativityOne documentation portal. The section on the tilde (~) operator describes its use for fuzzy searching to find words that "differ only by a few characters."

- Relativity - Searching. (n.d.). Using dtSearch syntax options. Relativity Documentation. Retrieved from the RelativityOne documentation portal. This page details various search syntax, including fuzzy searching, contrasting it with exact match methods.

A .dat file is the most common and conventional file format used for document-level load files in Relativity and the broader e-discovery industry. It is a delimited text file where each line represents a record (a document) and columns, separated by a delimiter, represent metadata fields. The delimiters are specified during the import process. While other formats like .csv or .txt can be used, .dat is the industry-standard extension for this type of file, and Relativity's tools are optimized for its use.

A. A .txt file can be used, but .dat is the more specific and common industry standard for this purpose.

C. An .xml file is used for specific import types, like the Native File Load Format, not for the common metadata overlay load file.

D. A .pdf is a document format itself and is the data being described by a load file, not the load file itself.

- Relativity. (2024). Load file specifications. Relativity Documentation. Retrieved from the Relativity Community portal. (This section explicitly discusses the use of .dat and .csv files as standard formats for load files.)

- Relativity. (2024). Importing document metadata, files, and extracted text. Relativity Documentation. Retrieved from the Relativity Community portal. (Examples and specifications consistently refer to .dat as the primary load file format.)

A coding layout, often referred to as just a layout, is a customizable web form used in the document review interface. It organizes fields and choices, enabling reviewers to input their decisions (e.g., 'Responsive', 'Privileged') and other relevant metadata for a document. Layouts are fundamental to the document coding process, providing the structure for capturing reviewer work product efficiently and consistently.

A. Search tool: Searching is performed using the search panel, saved searches, or dtSearch/keyword indexes, not a coding layout.

C. Backup file: A backup file is a copy of workspace data used for disaster recovery and is unrelated to the user interface for review.

D. Index: An index (e.g., a keyword or dtSearch index) is a data structure that facilitates fast text searching, not a user interface for coding.

1. Relativity Documentation. (n.d.). Layouts. Relativity Server 2023 Documentation. Retrieved from https://help.relativity.com/RelativityOne/Content/Relativity/Layouts/Layouts.htm. (The introductory paragraph states, "Layouts are web-based coding forms where users can view and edit document fields.").

2. Relativity Documentation. (n.d.). Building a layout. Relativity Server 2023 Documentation. Retrieved from https://help.relativity.com/RelativityOne/Content/Relativity/Layouts/Buildingalayout.htm. (This section details the components of the interface for document review).