Import production

When importing or loading production, you use templates to identify load files, DAT file specifications, and map field names. The process enables you to validate files and field mappings.

The Load folder must contain everything needed for the load, including the DAT, LST, and OPT file as well as the Images, Natives, and Text folders. For more information about the required folders, files, and file structure (for example fields, paths, and delimiters), refer to the Load file specifications topic.

While Loading, if the third-party data is a different time zone than that of the project time zone, Desktop Client allows you to select a time zone for this load. Desktop Client loads the data into the Epiq Discovery with the time zone selected in Desktop Client. In Epiq Discovery, in the Inspector Review page, the loaded documents display the metadata in Desktop Client time zone irrespective of the project time zone.

As needed, you can view the details of a submitted Loading job in the Jobs Overview page in Epiq Discovery.

Perform the following procedure to import production.

  1. In the Action page, click .
  2. In , select an existing template, or select and enter a template name.
  3. In , enter or update a name for the job in .
  4. For LOG FILE LOCATION, click to navigate to and select an output location for the log file.
  5. For (DAT), (OPT), and (LST), click to navigate to and select the load files to import.
  6. In , define how load creates new records or updates existing records using one of the following options.
    • - Loads all records as new records.
    • - Matches and then only updates existing records. If an imported records does not match an existing record, it is ignored.
    • - Matches and updates existing records. Creates new record for any imported records that does not match an existing record.
  7. In , the load file's encoding is automatically detected. You can override the detected method by selecting another option from the list.
  8. In TIME ZONE, select the desired time zone to load data. By default, this field displays the project time zone.
  9. In , select the delimiter used in the load file for each item in the list, including , , , and . If you select as the delimiter, you must supply the character to use in the resulting box.
  10. Click .
  11. Map each by data type.
    • To map standard data types, perform the following steps.
      1. Choose the type of data in the field.

      2. Select the associated field name.
    • To define a custom mapping, perform the following steps.

      1. Select as the type of data.

      2. In the dialog box, select a data type, add a name for the field, and click .

    • To exclude a field during mapping, in the data type, choose .

  12. To validate field mappings and files, click . If errors occur, each field mapping error shows a message and file errors appear in a report.
    1. To view file errors, in , click
    2. Review the resulting text file, make note of errors, and then close the file.

    3. In , click .
    4. Correct any errors and click . Repeat until no more errors appear.
  13. To save the template, perform one of the following steps.

    • To save a new template, click .

    • To save a template based on an existing template, click . When prompted, enter a name for the new template, click .

  14. When the successful template creation message appears, click .

  15. To perform the load, click . A message appears when the job completes.

    • If all files successfully load, you completed all steps.

    • If any documents fail to load, the message contains instructions on how to resolve the issues. If this occurs, navigate to the file locations mentioned in the message. View the latest <jobname.timestamp>.DAT file to find details about failed documents. The latest log file contains information about why any documents failed to load. Correct the errors for the failed documents in the <jobname.timestamp>.DAT file, and then perform this procedure again using that DAT file.