How to Import a Project

Home > selected Organization > Import Project

Users in a role with the required permissions can import a Project that was previously exported, either to make it available to other Organizations or users on other Reef ECA systems or to archive it, removing it from active use.

Deleting the Exported Project

If you are importing a Project exported on the same Reef ECA system, whether from the same or a different Organization, verify that the exported Project has been deleted from the Project list of the original Organization before you perform import it; if this is not the case, the import fails. If this happens, view the Home page status to confirm that the failure was due to the Project not having been deleted from the Project list before the import, or that there was another issue (for example, the database contained conflicting objects). In the latter situation, contact Reef ECA Customer Support to see whether the problem can be identified using the Reef ECA Leak Detection Utility.

To delete an exported Project prior to Project Import within the same system, to the same or different Organization:

  1. From the Home page, find the exported Project in the list of Projects for the associated Organization.
  2. Use the ellipsis menu or right-click the exported Project and select the Delete option.
  3. In the confirmation popup that appears, Request Project Deletion. This puts the Project into a DELETE_REQUEST_PENDING state.
  4. At this point, a System User iwith the required permissions must approve the deletion of the Project from the eDiscovery Delete Pending Projects screen. Once the deletion has been approved and the Project deletion process has started, the Project state on the Home Page changes to DELETE_PENDING. When the deletion process is complete, the Project no longer appears on the Home page, but instead on the Deleted Projects list.

Accessing the Exported Project

To import a previously exported Project, Reef ECA must be able to access the directory containing it. To ensure this, an importing user in the same Organization from which the Project was exported must identify and specify the project data area to which it was exported, while a user in a different organization or on a different Reef ECA system must obtain from the exporting Organization the mount point and path of the NFS connector and project data area used for the export, recreate them within their own Organization, and specify the project data area when importing.

Importing a Project

To import a Project:

  1. From the Home Page, for a selected Organization, right-click and select Import Project.
  2. For Name, specify a unique Project name (up to 100 characters) (unique within the Organization). The name can include alphanumeric characters, spaces, and some supported characters (such as a hyphen, underscore, and apostrophe), as well as characters from foreign languages (for example, Korean characters). However, the following characters are not supported: ! " # $ % & * + . / : ; < = > ? @ [ \ ] ^ { | } ~ “ ”
  3. Optionally, specify a description of up to 1024 characters in the Description field.
  4. For Project Data Area, select from a list of available project data areas (identified by the icon) the one that was used to export the project (if you are in the same Organization) or the one configured by your Organization Administrator to access the Project (if you are in a different Organization or on a different Reef ECA system). This populates the Folder area on the right, in which you must select the location of the exported project. If you are unsure of the correct project data area and/or folder, consult your Organization Administrator.
  5. Click Import Project to start the Project Import, or Cancel to cancel the operation.

You can monitor the state of the Project Import from the Home page. You will see Importing for a state while the Project Import is in progress, and the Project will become available when the Project Import completes. If the Project Import fails, you will see an Import Failed status. A tooltip will provide any available information concerning the failure.

In addition, all of the Work Basket tasks associated with the Project previously should appear in the Work Basket, and the Audit Log for the Project should contain all previous operations. If you do not see all expected tasks in the Work Basket after Project Import, use the Work Basket Tasks from all users option to show the tasks other users may have issued prior to Project Export.

Each imported Project will have the following from the previously exported Project:

  • Any Project Data Views previously included in the Project export (and their associated indexes). This includes Analytic views such as custodian views, batch views, and mediaid views.
  • Project settings, Tags and Tag states, Patterns, Export Settings, and Export Fields.
  • Scan Report state of each successfully indexed Data Set in the entire Project. (Any failed Data Sets or Do Not Index Data Sets are not preserved from the previously exported Project.)
  • Shared Data Sets that resided in the Project at the time of Project Export. If the Project contains a Shared Data Set from an Originating Project, the Shared Data Set is handled as follows:
    • If the Originating Project that marked the Data Set as Shared still exists, then the Shared Data Set will not be created upon Project Import and will instead reference the existing Shared Data Set.
    • If the Originating Project that marked the Data Set as Shared no longer exists, then the Shared Data Set will be created upon Project Import.
  • Project Audit Log
  • Any Synthetic Documents (for the entire Project
  • Email threading state (preserved if previously applied)
  • Clustering state (preserved if previously applied)
  • Export state (documents exported, document IDs)
  • Near Duplicate Group state (preserved if previously applied)
  • Appropriate Work Basket entries
  • Export Volume report information for previously performed Exports
  • Report information from a previous run of a Workflow or any Export Comparison Report, including search term report information, if appropriate, and any Custodian or Batch tab information eligible to appear in the download report. (If there is an unexpected error while exporting the report data at the time of the Project Export or when importing the report data, the Project Export and/or Project Import will not fail. In this situation, if you do not get the report data, you will need to validate and rerun a Workflow with the appropriate report options, or regenerate a standalone Export Comparison for a search result.)

In an imported Project, reports for views such as Imports, a Data Set, Project Data, a Custodian, a Tag, a Folder, or a Search result will be generated when you click the Reports tab for that view.

The following items are not retained from an exported project and have to reestablished in the imported Project:

  • Users from the exported Project. Users are not retained, so you will need to reestablish Users in the new Project after Project Import.
  • An Export Database configuration from the exported Project. If the previously exported Project included an Export Database configuration, you will need to reestablish the database using the Project-level Export Settings after the Project import. The new Project does not inherit the Project-level database configuration from the exported Project.