Importing Relativity Dynamic Object data via Import/Export

NOTE: This help topic is for use by Relativity Early Access customers only.

You can import data into Relativity Dynamic Objects (RDO) for use in Relativity applications. The workflow for RDO data import follows the same general guidelines as those for document load file imports.

If you want to use Import/Export with Express Transfer active, which is the recommended workflow for data transfer, refer to Express Transfer overview for more information.

Refer to Import/Export load file specifications and Data upload size limitation for more information regarding load files. Also see General recommendations for structured data import and export jobs.

To import RDO data:

  1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.

  2. On the Import/Export Job page, click the New Import/Export Job button to start a new job.

  3. On the Choose Workflow dialog, the Import button is selected by default. Next, click the Structured (Processed) Data workflow box to import a document load file to your workspace.

    Choose worflow for structured processed data

    Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active. See Activating and deactivating Express Transfer for more information.

  4. On the Choose the Load File type dialog, click the RDO box to import a load file to your workspace.

    Choose the Load File type

  5. If Express Transfer is not Active, skip this step. If it is Active, click Select on the Select data to Import dialog to browse to your local drive and select the folder with the files that you want to upload. In the case of universal naming convention (UNC) paths (for example, \\ServerName\SharedResourceName\FilePath), you can copy and paste the path into the Select Folder address bar in the dialog box to access the desired folder.
    Select data to import

    • You can choose only one folder with a load file to transfer.
    • File names must be 200 characters or less, including the extension.

    • We recommend using a local drive instead of a mapped or external drive to avoid potential slowness and connection issues with the file import process. Also see Data transfer performance considerations.
    • When Express Transfer is active, you should not zip data for importing.

    • When Express Transfer is active, it uploads only files linked in the selected load file, regardless of their location.

    • When Express Transfer is active, it ignores mismatches in upper and lower case between file paths in the load file and the actual file names.

    • When Express Transfer is active, it supports load files with relative paths, absolute paths, and UNC paths. It is possible to mix different path types in a single load file.

  6. On the Choose Load File and Location dialog, complete the following fields, then click Continue. Refer to Import/Export load file specifications for more information regarding load files.

    Choose load file and location

    • Job Name—provide a descriptive job name so that you can quickly identify and track that job on the Import/Export Job Page. The Job name field accepts up to 50 characters.
    • Relativity Object Type—select the Relativity object type from the drop-down list that you want to import data.
    • Profile—are job configuration settings that were previously saved to a profile file (.ie or .kw*) so they can be reused when creating future jobs with the same or similar settings in RelativityOne, which saves time and effort as well as helps prevent data entry errors when you're mapping fields, for example. Profiles with the ".ie" extension can only be used in Import/Export.

      • None—select this option if you do not desire to use a profile for this import or if you intend to create a new profile based on the settings entered in the upcoming steps. You will be able to save the profile settings later on the “Import settings” dialog. The file extension for the new profile created will be “.ie”.

      • From Local Disk Profiles—use this option to select a previously saved Import/Export profile (.ie file) or an existing .kw* profile (created via the former Relativity Desktop Client application) to reuse the job settings for this workflow. Use the drag and drop feature or browse for a file to choose it. All job settings provided within the selected profile file will be automatically entered where applicable in the succeeding workflow dialogs.

    • Regional Settings (Date and Time)—select the desired format for imported date and time data. A preview of the chosen format will appear below the selection. The setting selected will remain for all future jobs until you choose another one from the list or until you clear your browser cache. When browser cache is cleared, the setting will revert to the US date and time by default.
    • Load File—use the drag and drop feature or click browse for a file to select load file with RDO data from your local drive.
    • Include Native & Text—select this option to include native and text files.

      Note: The Include Native & Text option is not available for image or production import workflows as there are no native files included in OPT files.

    • Native & Text—if Include Native & Text was selected, use the drag and drop feature or click browse for a file to select the zipped native and text file from your local drive. See ZIP archive with extracted text and natives

    • (Optional) Notification Addresses—enable email notifications by providing the email addresses of those who should get notified once the job completed, failed, or canceled.

  1. On the Load File Settings dialog, select the delimiters and encoding values of the load file for the import, then click Continue. The File Column Headers Preview pane will help you to choose the proper settings.

Load File Settings

  • File Encoding—select an encoding format for the load file. Consult your processing vendor or department to determine the correct encoding option, if necessary.
    The File Column Headers Preview pane automatically updates when you select the File Encoding type. Since the load file is parsed based on the delimiter set, you may need to check delimiters used in the load file if the column headers are not lined up correctly. Determine the delimiters used in the file, and then select them in the delimiters section of this tab.

  • First Line Contains Column Names toggle—select this option if the first line contains column names.

  • Select the delimiters and encoding values used by your load file:

    • Column—select the character used to separate columns.

    • Quote—select the character used as the text qualifier.

    • Newline (Long Text Fields)—select the character used to indicate the end of a line in any extracted text or long text field.

    • Multi-Value—select the character used to separate choices within a field.

    • Nested Value—select the character used to separate the different levels of a multi-choice hierarchy.

  1. On the Fields Mapping dialog, select the load file fields to import and map them to the workspace fields, then click Continue.

    Load File Mapping

    To automatically map fields, click Auto Map Fields, and the fields from the load file will be mapped to any existing fields of the exact same name in the workspace. Any fields without a match will display "Choose..." in the Workspace Fields column and you will need to select one from the drop-down list. To search for a field in the list, begin typing the desired field name and matching search results display for selection.

    Consider the following when auto-mapping fields:

    • Case is not taken into account for the mapping. For example, a field named "email" in the load file would map to a field named "Email" in the workspace.
    • Spacing is taken into account. For example, in a two-word field name, if there is one space between words in the workspace field, and two spaces between words in the load file field, the fields will not be mapped.

    • Characters are mapped only to themselves. For example, an underscore is only mapped to another underscore, not to a space.

    Only fields matched or those with additional settings selected are loaded into the workspace. Other fields in the Load File Fields and Workspace Fields are ignored. You must always match the identifier field for the load file.

    Note: To import RDO data into a workspace, you must map the document identifier, whether it be Name, Control Number, or another field. If you do not, the import mode options will be limited and you will be unable to proceed with the import.

    Other options and fields on this dialog:

    • Create Field button—click this button if you want to create a new workspace field.

    • Export to CSV—click this button to save the field mapping configuration to a .csv file on your local drive.

    • Mapped to the top toggle—when turned on, this option groups all mapped fields on the top.

    • Load File Sample column—presents exemplary data from the load file fields.

    • Load File Fields column—provides the load file field names. Use the Filter box to search for field names.

    • Workspace Fields column—allows you to manually map the load file fields to the existing workspace fields. Use the Filter box to search for field names.

    • Additional Field Settings column—currently not supported.

  1. On the Import Settings dialog, configure your import job by selecting from which line number you want the load file to begin importing and how you want the records to be imported.

Import settings

  • Start Line—select the line number in the load file where you want the import process to begin. The default value is set to 0, which results in loading the entire load file.

  • Import mode—choose how you want the records to be imported.
    • Append Only—loads only new records.

    • Append/Overlay—adds new records and overlays data on existing records. If selected, then you must include an Overlay Identifier next.

      Note: For Append/Overlay and Overlay Only, if a blank metadata field exists in the load file (.dat, .csv), the blank value will overlay (remove) any existing value that may reside in the corresponding mapped field.

    • Overlay Only—updates existing records only. If selected, then you must include an Overlay Identifier next.

    • Overlay Identifier—if either “Overlay Only” or “Append/Overlay” mode is selected, then assign the unique identifier that will be used to overlay data in the workspace. This field acts as a link indicating to RelativityOne where to import the data.
  1. (Optional) Click Save Settings on the Import settings dialog to save the job configuration settings entered thus far to its own profile file (.ie file extension) on your computer so that you can reuse these settings when creating a new import job with Import/Export in the future

Note: Import/Export saves job configuration settings to its own profile file format (.ie file extension). Comparing to the legacy .kw* standard, it brings more flexibility as you now can apply saved job settings across various workspaces. The .ie profile file format is not supported in other RelativityOne data transfer tools.

  1. (Optional) Click Precheck Load File on the Import settings dialog to run a validation process on the load file to check for errors prior to importing it. All detected errors display in the Precheck window.

    Click the down arrow next to any error message to view its details. If you want to correct the errors in the source file(s) and repeat the importing steps, click Cancel to discontinue importing the file at this time. Otherwise, go to the next step to import the load file with errors and correct them later.

    The following validations occur during Precheck:

    • Date format
    • Field type
    • Field length
    • Number of load file cells
    • Number of folders and choice fields
    • File paths for natives and extracted text (checks 1,000 random lines across the whole load file)

    Note: The Precheck Load File summary dialog displays a maximum of 1,000 errors for each error category and will display a message indicating the total number of errors found. For example, if an error category has 2,000 errors, only the first 1,000 will display in the drop-down list.

Precheck Load File summary with error details displayedPre-check with folder validation

  1. Click the Import button to start the importing process.

  1. Review the importing progress on the Importing dialog. Real-time details regarding the number of transferred files and data size being processed displays during the Uploading and Extracting steps. If needed, click Cancel to stop the import job before it completes. Otherwise, click Close when the importing process is complete.

Caution: If you used Import/Export in web only mode (meaning Express Transfer was not active), do not close the Importing dialog until after the Uploading step has successfully completed. Closing the dialog prior to the Uploading step completing will terminate the data transfer (upload) process.

Importing progress dialog

  1. When the import is complete, the Import Summary displays. If no errors were found in the load file, go to the next step. If errors were found, the number and other information will be listed. You can do either of the following:

    Note: Only records that imported without errors will appear in the workspace.

    Import summary

    • To proceed without correcting the errors, go to the next step.
    • To manually correct them now, click the Download Error Load File button. Review the errors and correct them as needed. When done, upload the file with the corrected data by clicking the Select button on the Import Summary screen next to New Load File and navigating to the load file on your local drive. Once selected, click Import to import the job with corrected data.
  2. Click Finish to close the dialog.

You can review the Import/Export Job page to see more information about the job. Refer to Import/Export Job tracking and historyfor details.

For more information on where Import/Export saves files, see the Community article, Import/Export: Where Files Are Saved By The Import/Export Application.

Note: If you ran the job with Express Transfer active, you are able to close the Import/Export application while the job is running, if desired, and the transfer job will continue and not be affected. You can monitor the progress and history of jobs within Express Transfer (see Express Transfer Job tracking and history). You do not have to be logged into RelativityOne to view information within the Express Transfer application.