Create a Project

Home page > selected Organization > New Project

Only users with the required permissions (for example, an Organization Administrator) can use the New Project option; for more information, see View and Manage Role-Based Permissions.

Creating a Project includes the following:

  • Basic Information
  • Review platform integration, if applicable
  • Membership
  • Default Template Settings

Specify Basic Information

Assign a name and an optional description to the Project, as follows:

! " # $ % & * + . / : ; < = > ? @ [ \ ] ^ { | } ~ “ ”

Integrate with a Review System

If Reef ECA is connected to one or more review systems, the New Project dialog lets you choose to either integrate the new Project with either Reef Review or Relativity Server, or create a Reef ECA-only Project. Review integration lets you associate the new Project with one or more projects on the review system, to which Project Users will be able to promote (directly export) data. A dedicated Export Data Area is automatically created for each associated review project. For more information about how review system integration and promotion work, see Review Integration Overview.

  • Review System — This control gives you a choice between Reef ECA Only and the connected review system(s) — Reef Review, Relativity Server, or both . You can select only one option.

    Note: A Reef ECA only Project can be converted to a review-integrated Project at any time after creation using the Edit option for the Project on the Home page. A review-integrated Project, however, cannot be converted to a Reef ECA only Project (even if it was created as such) or to a different review platform (for example, from Reef Review to Relativity Server).

  • Review Project — When you select either Reef Review or Relativity Server from the Review System control, you must associate the new Project with at least one review system project. This setting gives you the following choices for doing so:

    • New associates the new Project with a single, automatically-created new project on the review system. When you select this for a Reef Review project, you must also select a Reef Review template to base it on using the control below.

      Note: To associate more than one new review project with the new Reef ECA Project, you can create the new projects on the review system first, then associate them as existing projects on the New Project page, as described below.

    • Existing lets you associate the new Project with one or more existing review projects. Click the green plus () to display the Select Review Projects dialog, which lists the projects you have access to on the review system, and select one or more of them. You can associate multiple review projects all at once, or one by one; each time you click OK on the Select Review Projects dialog, the review projects you added are displayed next to Existing on the New Project page. When you select a project that is already associated with an existing Reef ECA Project (which is valid but may not be desired in some cases), a pop-up alerts you to this.

      Note: You can associate additional review projects (including new ones you create as needed) with a review-integrated Reef ECA Project at any time by selecting Edit Project from the Project's context menu on the Home page. (You can also use Edit Project to convert a Reef ECA only Project to review-integrated.)

    • Review Template is visible only when you have selected Reef Review as the Review System and New as the Review Project. Clicking it displays the Select Review Template dialog, which lists the Reef Review templates you have access to so you can choose one to base the new review project on. You must select one and only one.

Note: If the Project is integrated with a review system (as described in the previous section), User and Group Project membership is transparently replicated in all associated review projects, including the creation of users and groups on the review platform as needed. Subsequent updates to the Reef ECA Project's membership are also replicated in associated review projects.

Establish Membership

Users in a System or Organization role with the required permissions can create a new Project and assign Users and Groups as members. The following information is listed for each member of a Project:

  • Type — The type of Project member. Organization Users and Organization Groups have explicit membership within a given Organization, while System Users and System Groups have explicit membership within one or more Organizations and are configured by a System User in a role with the appropriate System-level permissions.
  • Name — The assigned name of the User or Group
  • Role — The User's Organization role within the project. Like a System role, an Organization role represents a set of permissions to apply actions to objects. If you have the appropriate permissions you can select the default role (determined by the Set as Default option on the Role Permissions page), another of the predefined roles, or a custom role created for the Organization. By default, the predefined Organization roles have the following permissions:
    • Organization Administrator — Always has permissions to manage all Organization Settings and all aspects of Projects within the Organization; cannot be edited or deleted.
    • Project Administrator — Has view permissions for all Project Data nodes in the Navigation Tree and add/edit permissions for some of those nodes, such as Tags, Folders, Saved Searches, Workflows, Comparisons, and Synthetic Documents. Also has document-related permissions to add or remove Tags from documents and documents from a Folder, download native document and PDFs, and view document reports, as well as view permissions for some settings and the ability to edit the list of Metadata View Fields.
    • Project Member – Has limited permissions to perform general document search and analysis, but not to control any aspects of the Project.
    • Claimant — Used in Reef Claims (previously known as Class Action) Projects on a Reef Express system; not intended for use in eDiscovery.

When you create a Project, you are initially listed as the sole member. By default, if you are an Organization Administrator, System Administrator or System Manager, you can use the drop-down under Role to change your role within the Project, because these roles have the Role Permissions - Add/Edit permission.

Click Add / Remove Members to see the list of all Users and Groups that have a defined role in the Organization and add those you select as members of the Project. It is possible that some Users have only Organization Group membership and no individual role; their permissions are based on their Group role.

If the Project is integrated with a review system (as described in the previous section), User and Group Project membership is transparently replicated in all associated review projects, including the creation of users and groups on the review platform as needed. Subsequent updates to the Reef ECA Project's membership are also replicated in associated review projects.

Default Template Settings

The New Project page also lets you select one or more default templates for the Project. Default templates are used as a starting point for many different functions. For example, the default Metadata Search Fields template determines the starting lists of Available Fields and selected Metadata Search Fields when a User creates a new Metadata Search Fields template, whereas the Workflows contained in the default Workflows template are automatically added to the new Project so they are available to Project members run or use as the starting point for a new Workflow.

Because each drop-down is set to the predefined Default template (for example, Default Export Settings or Default Search Settings) you are not required to make any changes to this section, and should do so only where there is an available Organization or System template you think would be more useful as a general starting point than the predefined default. For example, your organization may have Export Settings templates designed for promoting data from review-integrated Projects to the relevant review system.

Note: There are no predefined Default templates for Excluded Content or Survivorship Model; these must be added to the Organization's templates by a User.
As of 5.2.5.x, all new Projects are created using Parsing Library Version V2, and only V2-based templates are available to be selected as the default for a new Project.

  • Alias Lists — For the lists of Aliases that you want to use in your Project. You must define Alias Lists for the template, since the initial template does not have any Alias Lists.
  • Billing Reports — For establishing File Type Exclusion Groups with the File Types you want to exclude from the billing reports for the Imports, Data Set, and Project Data views.
  • Custom Fields — For establishing custom fields that you want to display and use (for example, for a DAT Load File).
  • Domain Lists — For the list of email domains you want to recognize.
  • Excluded Content — For content that you want removed from the content index so that the content is not responsive to searches.
  • Export Fields — For the list of Export metadata fields you want to apply to data that you export from the Project.
  • Export Settings — For the list of Export Settings you want to apply to data that you export from the Project.
  • Index Settings — For parsing-related Index settings such as OCR processing, Language Detection, and Numeric Settings.
  • Load File Import — For establishing the settings and fields needed for a Load File Import (for example, a DAT Load File).
  • Metadata Search Fields — For the list of Metadata fields you want to be searched automatically as part of all term search queries (that is, as long as the Include Metadata option remains enabled, a keyword-based search is expanded to include the specified list of metadata fields). The system supplies a default subset of metadata fields, but you can choose which fields you want to include.
  • Metadata View Fields — For the list of metadata fields you want to view in the Project (for example, in the Document Viewer Metadata pane).
  • Patterns — For the list of patterns (regular expressions) you want to have applied during parsing.
  • Reports — For selecting the reports you want to have generated for Imports, a Data Set, and Project Data.
  • Search Settings — For the Search Syntax and Search Term Report options you want to use in the Project.
  • Survivorship Model — For the list of queries in a given order you want to employ as an email survivorship model used for document deduplication at Export (email or non-email deduplication). You must define queries for the model, since the default template does not include an queries.
  • Tags — For the set of Tags you want to make available for document tagging.
  • Workflows — For the Workflows you want to make available for use or as starting points for creating new ones.