Step 2: Load a Case Definition

About Case Definition Options

The second step in creating a case in Eclipse is typically that of defining needed database fields.

Note: Each case can include a maximum of 500 fields.

This step can be accomplished in one of four ways:

  • Option 1: Copy the definition of an existing case.

  • Option 2: Use a case definition (.CSE) file.

  • Option 3: Use a load file (typically a .CSV, .DAT, .DLF. or .TXT file).

  • Option 4: Define all aspects of the case manually.

Choosing the Correct Option

  • For a new case being created in Eclipse, any of these methods may be appropriate, depending on your circumstances.

  • For a case created in eCapture and being enabled in Eclipse, you will typically choose Option 3 and select the load file created during the eCapture export (optimally, a .DAT file) to ensure that the fields in Eclipse match those created in eCapture. Refer to your eCapture case and documentation for details on the fields in the case.

Field Types

Regardless of the method chosen, Eclipse includes the following system fields (even if they are not included or defined during case definition).

Basic system fields:

BEGATTACH

BEGDOC

CUSTODIAN

DOCUMENTDATE

DOCKEY

ENDATTACH

ENDDOC

EXTRACTEDTEXT

EXTRACTEDTEXTSIZE

MD5HASH

 

File-related fields:

HASIMAGE

HASNATIVEFILE

NATIVE

NATIVEFILEEXTENSION

NATIFEFILESIZE

NATIVEFILETYPE

NATIVEFILETYPEDESC

 

OPEN DISCOVERY imaging fields:

OPEN DISCOVERY IMAGINGERRORS

OPEN DISCOVERYIMAGINGERRORFLAGS

OPEN DISCOVERYIMAGINGJOB

OPEN DISCOVERYIMAGINGSTATUS

ClosedOption 1: Copy from an existing case

Select this option to use the case definition of an existing case for your new case. The following case details will be copied. All details can be modified for the new case if needed.

  • Database field names and types (system field names can be changed)

  • Tag palette

  • Redaction palette

  • Noise (stop) words

  • Case options (tagging level, date/time format options)

To copy from an existing case:

  1. After completing Step 1: Set Up a Case, click the Step 2. Load Case Definition tab.

  2. Select Option 1.

  3. Select the needed managing client and case.

  4. Review the copied case fields; take one of the following actions:

  5. Continue with Step 3: Define Database Fields to make changes to field definitions or add/remove fields.

  6. If no changes are needed to fields or you want to complete field definitions later, continue with Step 4: Select Case Options.

ClosedOption 2: Load from a case definition file

Eclipse Administration allows you to create case definition (.CSE) files, which can serve as “templates” for future cases. Case definition files specify the following aspects of a case:

  • Database field names and types

  • Tag palette

  • Redaction palette

  • Noise (stop) words

  • Coding forms

  • Relationships

  • Case options

For details on creating case definition files, see Export a Case Definition File.

Note: To use this option, the .CSE file must have been exported from IPRO Eclipse 2013 or later.

To use a .CSE file as the basis for your new case, complete the following steps:

  1. After completing Step 1: Set Up a Case, click the Step 2. Load Case Definition tab.

  2. Select Option 2.

  3. Click the  button corresponding to Option 2 to navigate to the needed .CSE file.

  4. Select the file and click Open.

  5. In the Case Definition dialog box, review the summary information, then select the type of case detail that you want to copy into the new case:

    Option

    Description

    Select All

    All detail in the .CSE file will be used for the new case.

    Database Fields

    Field names, types, and option settings

    Tag Palette

    Tag groups and tags

    Redaction Palette

    All aspects of each redaction category

    Noise Words

    Words to be excluded from searching (stop words)

    Coding Forms

    “Field sets” defined for the Record pane in Eclipse.

    Relationships

    Related-document details as defined in the .CSE file

    Options

    Tagging level, date/time format options.

     

    Note: To use this option, the .CSE file must have been exported from IPRO Eclipse 2013 or later.

  6. When selection is complete, click OK.

 

ClosedOption 3: Load from a data load file

Note: To migrate an entire case directly from Concordance, see Migrate Cases from a Third-Party Database.

If you have any of the following types of data load file, use it to define the database fields of the case you are creating:

Load File

Description

.CSV[1]

A delimited ASCII text file typically with a delimiter format of quote-comma-quote or commas.

DAT[1]

A delimited ASCII text file containing field data and metadata exported from IPRO eCapture, LexisNexis Concordance, or other product that can create such a file.

DLF[1]

A type of IPRO load-file format for the legal industry. It is an .XML file created when a case or data is exported from IPRO Eclipse (or other sources). A .DLF file can include most case characteristics.

.DII

A Summation Document Image Information load file. An ASCII text file formatted using a non-delimited, multiple line format.

TXT[1]

Plain text file (such as one saved from Concordance, Microsoft Excel, or another database system).

.LFP

IPRO Tech load file for image data.

.OPT

Opticon load file for image data.

 

[1]For these load files, the field type for all fields defaults to FixedLengthText.

 

Procedure

To use one of the listed data load files to define the fields for your new case:

  1. After completing Step 1: Set Up a Case, click the Step 2. Load Case Definition tab.

  2. Select Option 3.

  3. Click the corresponding button and navigate to the needed file.

  4. Select the load file and click Open.

  5. Delimiters: If you are using a DLF or DII file, skip to step 6. Otherwise, check the default delimiters and change if needed.

    Default delimiters are comma (,) and quotation mark (") for Field and Quote, respectively. If these delimiters are used in your data load file, skip to step 6. If other delimiters are used, select them as follows.

    Note: The Field delimiter is the character that separates each field. For example, for .CSV files, it is a comma; for Concordance .DAT files, it is typically an ASCII 20 control character. The Quote delimiter is optional. If used, it is the character that marks the beginning and end of a field’s content. For .CSV files this is normally a quotation mark. For Concordance .DAT files it is the ASCII 254 character. If the Quote delimiter is not applicable to your data, any entry in this field is simply ignored.

    1. In the Field list, select Custom.

    2. Click the option for the type of entry you want to make (text characters or ASCII character code).

    3. For characters, enter the needed character in the top field of the Characters column. The ASCII value appears beneath your entry.

    4. For ASCII values, enter the needed value in the top field of the Ascii Values column. The character appears beneath your entry.

    5. Click OK.

  6. Encoding: Select the character set to be used. Common encodings are available for selection.

  7. Review the copied case fields; take one of the following actions:

ClosedOption 4: Use a blank template

If you are starting “from scratch” and do not have an existing case or file on which your case can be based, follow these steps:

  1. After completing Step 1: Setting Up a Case, click the Step 2. Load Case Definition tab.

  2. Select Option 4.

  3. Continue with Step 3: Define Database Fields.

 

Next Steps: Step 3: Define Database Fields