As an example of using objects to extend data reach, from within a workspace, you can create your own RDO for storing custodian information, including not only custodian names but also their emails, sent and received dates, and recipients. This information can then link to other documents or for greater granularity in sorting, searching, or listing those documents.
This page contains the following sections:
See these related pages:
- Editing Relativity Objects
- Deleting object dependencies
- Creating a custodian object
- Creating a question object
- Updating new custodian field
- Applying custodian data
- Building Media Tracker with Relativity Dynamic Objects
- Creating a tab to bookmark an object
Also see these related recipes:
System objects are objects that come with Relativity applications by default. They are predefined objects that either load during installation, you can create during a Relativity session, or Relativity creates automatically during a process or because of a workflow. They include items such as workspaces, documents, fields, and OCR sets. However, Relativity sets their capabilities and you cannot change the design of them. For example, a system object may limit the number of fields that attach to it, or prohibit adding event handlers and object rules.
RDOs are objects you define. You can set their capabilities, such as specifying fields attached to them, managing data links to other objects, and allowing additional features including attaching event handlers and object rules. You create RDOs in a workspace, or by a system admin in the Home page, through the Relativity UI directly, such as from the Create New Object button of the Object Types tab, or indirectly, such as through the Event Handler Express application. Examples include question, and custodian objects. See Editing Relativity Objects.
Using Relativity Dynamic Objects
Imagine you're a system admin and your firm's latest case involves email exchanges between many people with various roles at many different companies. The lead attorney approaches you with ideas for organizing all the custodians, their companies, and their various roles within those companies. You decide to use RDOs to store information about a custodian by creating a custodian object. This object stores information about the custodian - their name, company, role, start date, and so on.
You then connect the custodian object to any related objects such as the document and company objects in the following example.
Using objects in your workspace helps keep items organized in your doc set.
You can also create and use objects programmatically with the Services API.