Select Mapping Options

After completing field mapping discussed in the previous procedures, complete the following procedures as they apply to your data.

This page contains the following content:

Check/Correct Path Information

You can easily check any file path information (for images, native files, and/or text) contained in the load file and change it to “point to” the correct location for the files being added to the Eclipse case.

To change path information for files used in Eclipse case:

  1. If you are working with a .DAT, .DLF, or .CSV file that includes a file path in the EXTRACTED TEXT field instead of the text itself, ensure that the Import Text from Path option is selected.

  2. On the Step 2 tab of the Import Data screen, locate a mapped field that includes a file path/file name (image or native path, or extracted-text file path), click  next to the mapped details. Eclipse will check the path and file name.

    • If the specified file exists at the specified location, a success message will display. Click OK and skip to step 4.

    • If the specified file does not exist at the specified location, an error message will display. Complete step 3.

  3. To correct file paths, click OK in the error message and complete the Edit Path dialog box as follows:

    1. Load File Path: Review the path information to determine the part of the path that is incorrect and needs to be replaced.

    2. Replace Text: Enter the incorrect portion of the load file that you identified in step a.

    3. With: Enter the correct file path information. (For images, this can be the path itself or a volume name that represents the correct path details. If entering a volume name, precede and follow the volume name with the “at” sign, @, as in @VOL1@.)

    4. Imported Path: Review the corrected path for accuracy.

    If needed, click  to update the path in the Imported Path field.

    For volumes (image path only), the complete path represented by the volume (and the portion of the load file path that you are not replacing) displays beneath the Imported Path field.

    1. To verify that the path is correct, click . If the file is not found, check your work and make corrections as needed.

    2. When the validation message states File found!, click OK.

    		4.

    Tip: You can copy path details from the path in the Load File Path field and paste it in the Replace Text field.

    If the path you enter is not valid, check your entries carefully. For example, look for missing or extra backslashes.

  4. Repeat these steps for each type of path in the load file.

  5. As needed, continue with another procedure described in this section. If no additional options on the Step 2 tab need to be set, go to Pre-Processing.

Select Import Mode for Data

Complete the following steps to define how data will be added to a case.

  1. On the Step 2 tab of the Import Data window, in the Select Mode section, select the way in which data is imported into the Eclipse case.

    2. ClosedImport Options

    Import Option

    Option

    Description

    Append All Records

    Use this option to add new records to a new or existing database.

    • For a new case, all records in the load file will be added to the database.

    • For an existing case:

    • Records in the load file that do not currently exist in the case will be added to the database.

    • Records in the load file that are also in the existing case are ignored.

    The load file must contain a BEGDOC, DOCID, or IMAGEKEY field.

    Overlay/Append

    Load File “Pet” Field

    Eclipse Case “Pet Field”

    (Before Import)

    (After Import)

    dog

    (blank)

    dog

    cat

    dog

    dog

    dog

    (blank)

    dog

    (blank)

    Overlay Only

    Use this option to update existing records. Selected records can be updated as described in step 2.

    • Records in the load file that do not currently exist in the case will be ignored.

    • Records in the load file that are also in the existing case will be overwritten (see the previous example).

    Tag Import

    Use this option to import tags and apply them to records in the Eclipse case as described in Tag import details.

     

  2. Overlay Field to Match: If you select either of the Overlay options in step 1, select the field (BEGDOC) to be used for matching the load file records to the case records field.

  3.  As needed, continue with another procedure described in this section. If no additional options on the Step 2 tab need to be set, go to Pre-Processing.

Tag import details

This information supplements Select Import Mode for Data. Tag details can be imported using a plain text file (such as a .CSV or .TXT file) containing image keys and tag information for each record for which tags are to be applied. The following figure shows the content of a typical text tag-import file.

Tags defined in the import file will be created in the Eclipse case if they are not already defined for the case.

To import tags successfully, the issues in the following table must be addressed.

ClosedTag Import Issues

Issue

Description

File Format

  • Make sure the First line is header option is not selected when you complete Select the Data Source.

  • Make sure the import file does not contain a header line.

  • Ensure each line of the file contains no more than one tag definition (either a tag, a tag group»tag, or tag»nested tag).

  • If tag groups are to be imported, every line of the file must include a tag group»tag entry. For example:

Wrong:

ECL00001|CONFIDENTIAL»CONF1

ECL00001|CONF2

Right:

ECL00001|CONFIDENTIAL»CONF1

ECL00001|CONFIDENTIAL»CONF2

Delimiters[1]

When you complete Select the Data Source:

  • Make sure the correct Field delimiter is defined.

  • If the import file includes tag groups and/or nested tags, make sure the correct Nested Field delimiter is defined.

Overlay field

When you complete Select import mode for data, make sure the Overlay Field to Match is set to the BEGDOC field.

Import options

Before performing the import, address the following:

  • Page tags: determine whether tags should be applied to documents or individual pages.

  • Private tags: determine whether private tags should be imported.

  • Tag groups: determine whether the import file includes tag groups or nested tags. See the previous figure for details.

These options are selected during Complete the Import.

Undefined tag groups are placed in an “Imported Tags” group.

[1]The delimiters used in the examples in this topic are common but not required. Delimiters in your file may be different.

 

Select Image File Options

Complete the following steps to select image handling options and correct the image path if needed.

  1. Ensure that the Step 2 tab is selected on the Import Data screen.

  2. Image Options: If you are importing data into a new case that contains no data, leave the default selection and go to step 3.

    3. Important: If you are importing an .LFP file that does not include IM lines, these options do not apply. (That is, the file contains OT, OI, and/or FT, lines only.) In this case, leave the default selection and go to step 3.

  3. For other types of load files, select one of the following options:

    • Create error if image exists: If the image key specified in the import file exists in the case, an error is logged and the image record is not created.

    • Overwrite and remove existing annotations: If the image key specified in the import file exists in the case, overwrite the record and eliminate any annotations (highlighting, mark-ups, and/or redactions) that were specified for the image.

    • Overwrite but retain existing annotations: If the image key specified in the import file exists in the case, overwrite the record and keep any existing annotations (such as highlighting, mark-ups, and/or redactions) that were specified for the image.

    • Skip existing images: If the image key specified in the import file exists in the case, leave the record for that image unchanged.

  4. Image file path: If the path defined in the load file for image files in the load file is incorrect and you did not make corrections during field mapping, click Edit File Path in the Image Options area and complete the Edit Image Path dialog box:

    1. Load File Path: Review the path information to determine the part of the path that is incorrect and needs to be replaced.

    2. Replace Text: Enter the incorrect path details identified in step a. For example, if the server name in the load file path is wrong, enter the incorrect server name.

    3. With: Enter the correct file path information, either the path itself or a volume name that represents the correct path details. If entering a volume name, precede and follow the volume name with the “at” sign, @, as in @VOL1@. For details on volumes, see Work with Image Paths.

    4. Imported Path: Review the corrected path for accuracy. If needed, click to update the path in the Imported Path field.

    5. For volumes, the complete path represented by the volume (and the portion of the load file path that you are not replacing) displays beneath the Imported Path field.

    6. To verify that the path is correct, click . If the file is not found, check your work and make corrections as needed.

  5. When the validation message states File found!, click OK.

  6. As needed, continue with another procedure described in this section. If no additional options on the Step 2 tab need to be set, go to Pre-Processing.

Select Text Options

If text files are being imported as part of the load file, complete the following steps.

  1. Ensure that the Step 2 tab is selected on the Import Data window.

  2. If you are working with a .DAT, .DLF, or .CSV file that includes a file path in the EXTRACTED TEXT field instead of the text itself, ensure that the Import Text from Path option is selected.

  3. If the path defined in the load file for text files is incorrect and you did not make corrections during field mapping, click Edit File Path in the Text Options area and complete the Edit Text Path dialog box:

    1. Load File Path: Review the path information to determine the part of the path that is incorrect and needs to be replaced.

    2. Replace Text: Enter the incorrect path details identified in step a. For example, if the server name in the load file path is wrong, enter the incorrect server name.

    3. With: Enter the correct file path information. For example, if the server name in the path is wrong, enter the correct server name.

    4. Imported Path: Review the corrected path for accuracy. If needed, click  to update the path in the Imported Path field.

    5. To verify that the path is correct, click . If the file is not found, check your work and make corrections as needed.

    6. When the validation message states File found!, click OK.

  4. As needed, continue with another procedure described in this section. If no additional options on the Step 2 tab need to be set, go to Pre-Processing.

Correct Native File Paths

If the path defined in the load file for native files is incorrect and you did not make corrections during field mapping, complete the following steps.

  1. Ensure that the Step 2 tab is selected on the Import Data window.

  2. In the Native Options area, click Edit Native File Path and complete the Edit Native Path dialog box as follows:

    1. Load File Path: Review the path information to determine the part of the path that is incorrect and needs to be replaced.

    2. Replace Text: Enter the incorrect path details that you identified in step a. For example, if the server name in the load file path is wrong, enter the incorrect server name.

    3. With: Enter the correct file path information. For example, if the server name in the path is wrong, enter the correct server name.

    4. Imported Path: Review the corrected path for accuracy. If needed, click  to update the path in the Imported Path field.

    5. To verify that the path is correct, click . If the file is not found, check your work and make corrections as needed.

    6. When the validation message states File found!, click OK.

  3. As needed, continue with another procedure described in this section. If no additional options on the Step 2 tab need to be set, go to Pre-Processing.

Choose Index Option

Select the Index after process completes option to create the index used for text searching after the import process completes.

To skip indexing now (for example, to save time), do not select the option. Indexes can be managed after data is imported as explained in Manage Indexes.