Transferring (promoting) data between workspaces

Complete the following fields in the Setup layout:

• Name—the name of your integration for reference purposes.
• Type—select Export to designate this as an export job. Selecting this sets the Source field to be Relativity.
• Source—this is automatically set to Relativity since you are exporting data out of a Relativity workspace.
• Destination—select Relativity.
• Transferred Object—select the available Document or non-document object meta data you want to transfer to the destination workspace. The non-document object must already exist in the destination workspace. The data transfer process will not transfer custom objects created by users in a workspace. Refer to the Notes above for additional information.
  
  Notes: You will need to create a new integration point for each object type that you want to export to the destination workspace.
  
• Profile—use this to complete the remaining Integration Points settings based on the settings of a saved profile. This includes all of the fields in the Connect to Source layout, as well as field mappings. If no profiles exist in the workspace, you do not have the option of selecting them. To apply a profile that you have already created, select it from the drop-down list. For more information on profiles, see Integration Points profiles.
• Email Notification Recipients—enter the email addresses of those who should receive notifications of whether the integration point export succeeded or failed. Use semi colons to separate email addresses.
• Log Errors—select Yes or No to denote whether Relativity tracks item-level errors.
  • If you select Yes, each job also logs any item-level errors.
  • If you select No, Relativity does not log these item-level errors.

Regardless of your selection, job-level errors are always recorded in Relativity.

• Enable Scheduler—gives you the option of scheduling additional exports. Selecting Yes makes the following fields available:
  • Frequency—the interval at which Relativity runs this integration point.
    • Daily—select this option to transfer data once every day.
    • Weekly—select this option to transfer data on a weekly basis. You can specify how often in the Reoccur field, in which you will provide a number value in the Every # week(s) choice. You can then specify on which day of the week the data transfer will take place by checking any of the days of the week listed.
    • Monthly—select the day of the month that you want this integration point to transfer data once every month.
    • Reoccur—enter the number of month(s) in which this integration point repeatedly transfer data.
    • Send On:
      • Day __ the month—select the day of the month that you want this integration point to transfer data.
      • The __ of the Month—select this option for this integration point to transfer data on the chosen day of every month. For example, "The Second Friday of the month."
• Start Date—the date that you want Integration Points to start transferring the data.
• End Date—(Optional) the date that you want Integration Points to stop transferring the data. Leaving the End Date blank causes the integration point to run indefinitely at the scheduled interval.
• Scheduled Time—the time at which this integration point transfers data. This time is local to your PC, not to the server.

Complete the following fields in the Connect to Source layout:

• Source—select Document as the transferred object during setup, then select Saved Search or Production from the drop-down list. If you select any other object as the transferred object during setup, this is automatically set to View.
• Saved Search/Production/View—depending on the selected Transferred Object, one of the following fields displays:
  • Saved Search—select an existing saved search to use from the drop-down list or click the ellipsis button for an alternative way to select a saved search.
  • Production Set—select an existing production set to use from the drop-down list.
  • View—select an existing view to use from the drop-down list.
• Destination Workspace—select an existing workspace to export your saved search or production to.
  

Note: Relativity will validate whether the selected object is available in the destination workspace and transfer only objects linked to Relativity Applications installed in the destination workspace. If the selected object is not available in the destination workspace, an error message will appear.

• Location—select a folder or production set as the destination location.
  • Folder—select the drop-down menu to expand the folder structure, locate the folder from which you want to export the data, and select it. This field is only available if you have selected Folder.
    

  Note: When creating an integration point based on a profile, if you change the saved search, folder, or production set on the Setup layout, the fields listed in the Selected Fields window below are not updated to reflect the new source that you selected. If you're not using a profile to creating the integration point, these fields are updated to reflect the newly selected source.

• Production Set—select a production set to export the data to. Click the plus sign to create a new production set. For successful operation, transfer Production Set with Append/Overlay mode.
• Create Saved Search—select Yes to create a saved search in the destination workspace. This saved search's name will take the name given to the integration point. This choice is enabled only if Yes is selected for the Tag Documents with Job Name field.
• Tag Documents with Job Name—select one of the following options below. See Considerations for document count considerations:
  • Yes (Source and Destination Workspaces)—to tag all documents in the scope of the job with a unique ID in both the source and destination workspaces, which allows you to easily identify these documents in both workspaces. This is the default option.
  • Yes (Destination Workspace Only)—to tag all documents in the scope of the job with a unique ID in the destination workspace only, which allows you to easily identify these documents in the target workspace. 
  • No—to not tag documents with a unique ID in either workspace.
    

Note: If you intend to use Smart Overwrite option during the Map Fields process next, you must select No or Yes (Destination Workspace Only) for document tagging.

In the Field Mappings wizard, you have the following options for mapping fields:

• Use the Shift+click and Ctrl+click method to select multiple fields at a time.
• Use the text search boxes above the Source and Destination lists to find a particular field.
• Use the single and double arrows or double-click a field to move selected fields between columns.
• Use the horizontal scroll bar in each column as needed to fully view long field names.
• Each column displays the total number of fields available in that column. This allows you to quickly compare the number of mapped fields to ensure they match. If they do not match, an error will display when you attempt to save the Integration Point.
• The field names in the Destination column include the type of each field listed.
• Click the Map All Fields button between the Source and Destination columns to automatically map all fields with matching names, except single or multiple object fields. If you have Destination fields that are mapped to Fields in the Field Catalog, Relativity also tries to find name matches between these Catalog Fields.
  Notes:
  • The Field Mappings process excludes certain fields that are used internally by the Integration Points application. The following fields are excluded from the Source and Destination lists: Relativity Source Case, Relativity Source Job, Relativity Destination Case, ErroredDocuments, Job History, and Document.ProcessingFileID.
  • If the WebAPIPath instance setting in the kCur.IntegrationPoints section is not configured correctly after upgrade or installation, the Source field list will not be able to display any attributes and will be empty. As a result, you will not be able to map fields.
  • You don't need to map all attributes or fields. Only the Unique Identifier and Object Identifier are required. The Unique Identifier should contain a value that no other item in the workspace contains. For example, use the GUID or distinguishedName attribute. The Object Identifier is the specific field on the object that holds the displayed identifier, which might not be unique. For example, the Full Name field is the Object Identifier of the Entity RDO but it might not be unique. These two identifier values can be the same.
• Click the Map Saved Search button between the Source and Destination columns to automatically map fields that were configured in the Saved Search, which was selected as a data source on the previous screen. If you have Destination fields that are mapped to Fields in the Field Catalog, Relativity also tries to find name matches between these Catalog Fields.

Note: The Map Saved Search functionality only supports searches created with a Keyword Search. Other search conditions, such as dtSearch and Analytics Indexes, are not yet supported for this functionality.

Complete the following fields in the Settings category:

• Overwrite—determines how the system overwrites records once you transfer data to the review workspace.
  

• Append Only—transfer only new records into the review workspace.
• Overlay Only—update existing records only in the review workspace. Any documents with the same workspace identifier are overlaid. When you select this option, you must complete the Multi-Select Field Overlay Behavior field described below.
• Append/Overlay—adds new records to the review workspace and overlays data on existing records. When you select this option, you must complete the Multi-Select Field Overlay Behavior field described below.
• Multi-Select Field Overlay Behavior—determines how the system will overlay records when you push documents to the review workspace. This field is only available if you've selected either Overlay Only or Append/Overlay above. This field provides the following choices:
  • Merge Values—merges all values for multi-choice and multi-object fields in the source data with corresponding multi-choice and multi-option fields in the workspace, regardless of the overlay behavior settings in the environment.
  • Replace Values—replaces all values for multi-choice and multi-object fields in the source data with corresponding multi-choice and multi-option fields in the workspace, regardless of the overlay behavior settings in the environment.
  • Use Field Settings—merges or replaces all values for multi-choice and multi-object fields in the source data with corresponding multi-choice and multi-option fields in the workspace according to the overlay behavior settings in the environment.
• Smart Overwrite checkbox—select if you want to only transfer the documents that were modified or added to the saved search since the last time the job ran. The benefit of selecting this option is that it may reduce the job processing time due to the reduction in the number of documents needing to be transferred. If this box is not selected, all documents are transferred regardless of whether they were modified or added.
  • If Smart Overwrite is used with Append Only: only the new documents that have been added to the saved search are transferred.
  • If Smart Overwrite is used with Overlay Only: only documents that have been modified in the source saved search are transferred.
  • If Smart Overwrite is used with Append/Overlay: both new and modified documents are transferred.

Notes:
• Smart Overwrite only works when the Tag Documents with Job Name option under Connect to Source is set to No (disabled) or Yes (Destination Workspace Only).
• Smart Overwrite works for specified conditions of the configured Integration Point, including Saved Search. If the Saved Search conditions are changed, then it is recommended to run the next execution of the Integration Point job with Smart Overwrite disabled in order to create a new baseline for further jobs within this Integration Point.
• If a Smart Overwrite job results in errors and they are not resolved with the Retry Errors option, then it is recommended to re-run errored documents transfer with Smart Overwrite disabled. Otherwise, the Smart Overwrite job will not pick the errored documents in the next execution.

• Copy Images—determine whether you want to copy images to the destination workspace:
  • Yes—click if you want to copy images to your destination workspace Then select options in the Image Precedence and Copy Files to Repository fields.
  • No —click if you don’t want to copy images to the destination workspace. Then select options in Copy Native Files and Use Folder Path Information fields.
• Image Precedence—this field appears when Yes is selected for Copy Images. Select Original Images or Produced Images to copy to the destination workspace.
• Copy Files to Repository—determine if you want to copy physical image files to the destination workspace:
  • Yes—click if you want to copy physical image files to the destination workspace.
  • No—click if you want to add reference links in the destination workspace directing to images located in the source workspace. Links to the images will be accessible in the destination workspace Viewer.
• Production Precedence—this field displays when Produced Images is selected for Image Precedence. Use the pop-up screen to select and order the productions, and click OK on the screen to save.
• Include Original Images If Not Produced—this field displays when Produced Images is selected for Image Precedence. Select this checkbox to include the original image.
•  Copy Native Files—if No was selected for Copy Images, determine how to copy native files to the destination workspaces by selecting one of these radio buttons:
  • Physical files—select to copy any physical native files from the source workspace to the destination workspace.
  • Links Only—select to add only reference links in the destination workspace that direct back to the source workspace documents. No physical files will be copied to the destination workspace, but native files will be accessible in the destination workspace Viewer.

Note: We do not recommend overlaying documents’ native files with Links Only option from Review workspace back to Repository workspace. This action may lead to overlaying the original native file with its link, that has been previously sent to Review workspace. And that will result in deleting the native file and the data loss. When choosing this option to transfer documents by only using links from repository to review workspace, be aware that the links to the transferred documents will be broken in the review workspace if you delete the native files in the repository workspace or if you delete or archive the repository workspace itself. In this situation, if you wanted to maintain the files in the review workspace, you first need to transfer the physical files to that workspace before deleting them from the repository workspace or before deleting or archiving the repository workspace. For details on transferring subsets of data, see Repository workspace special considerations.

Note: Be aware that when a non-administrator user copies native files by selecting the Links Only option, the System Created by column on the Job History tab will list the system administrator’s name instead of the non-administrator user's name.

• No—select to not create additional copies of your native files. No physical native files or links will be pushed to the destination workspace. You will not be able to look at native files in the Viewer. Only metadata, such as extracted text or coding decisions, will be pushed. For example, if you have a document with native files and coding decisions, and you select the No option, only metadata (the coding decisions) will be transferred to the destination workspace. Refer to additional notes below regarding this choice:
  •  Doing this maintains a single copy of that data file no matter how many times you use the document in your workspace.
  • You have the option of selecting No for an initial run of an integration point and then Yes for a subsequent run. Doing this saves you time on the initial job while then retaining copies of the native files on the final job. 
  • The benefit of selecting No for this field is that you save on storage and speed. 

• Use Folder Path Information—use a metadata field to build the folder structure for the documents that you transfer to the review workspace.
  • No—select if you don't want to build a folder structure based on metadata. In this case, Relativity loads all documents directly into the folder indicated by the transfer destination, and you create no new folders in the destination workspace.
  • Read From Field or Read From Folder Tree—select to use a metadata field to build the folder structure for the documents that you transfer to the review workspace.
  • Folder Path Information—specify a metadata field to build the folder structure for the documents that you transfer to the review workspace.
    • You have the option of creating folders or re-foldering documents when you select Append/Overlay for the Overwrite field.
    • You have the option of re-foldering documents for the Overwrite field through the Move Existing Documents field.
• Move Existing Documents—re-folder documents that were previously imported into the destination workspace, but were only placed in the root case folder and not to any subfolders. This field is useful for situations in which you want to add new data to the destination workspace while overlaying existing data.
  • Select No if you don’t want to re-folder existing documents.
  • Select Yes to move existing documents into the folders provided in the Folder Path Information field. For example, you previously imported custodian Sally Smith's files into the destination workspace's root folder. Now, in addition to placing the documents from the saved search specified in this integration point in their subfolder, you also want to move those previously migrated documents into Sally Smith's subfolder, so you would select Yes.

During the mapping process, Relativity validates whether the selected objects are available in the destination workspace in the final step of the wizard. When fields cannot be mapped from the Source to the Destination, a pop-up modal displays them. You can either choose to keep the fields in the Source column or skip them and remove them.

Another solution that Integration Points data transfer provides is automatically remapping fields when the destination workspace is changed. When you change the destination workspace in either the integration point or integration point profile, fields can vary between the source and destination workspace. When the destination workspace is changed, the new fields in the workspace are automatically mapped.

The artifacts are mapped based on their names only if the ArtifactIDs are different in the new destination workspace. They are mapped so that the integration points job will not fail. This means that if the source workspace fields cannot match to the new destination workspace fields, those unmatched fields are presented at the end of the mappings list for easy identification. Relativity also informs the you that the original source fields from the profile were mapped with corresponding fields from the destination workspace. The message will be similar to this, "We restored the fields mapping as destination workspace has changed."