A Detailed review of Summation
The CT Summation Blaze LG product family helps you efficiently manage case information such as transcripts and documents with the benefits of full-text imaging, PDF support, electronic evidence support and comprehensive production tools.
Summation to load and check DII File DII File:
A DII file is a specially formatted ASCII text file that can be created within any text editor. The DII file uses a non-delimited, multiple line format. Each record ends with the image filenames themselves. The data from the file is loaded into Summation’s Core Database and establishes the link between the database summaries and the associated images and OCR documents.
DII FILE COMPONENTS
@T (Image Tag) Required for each DII record. Must be used before any @C tokens for each DII record. Each instance of a line beginning with the @T token causes Summation to create a new database record or overwrite an existing one. If the value that follows the @T line does not match an existing record number in the active table (usually either the STDTABLE or the ETABLE) then a new record with that number is created. If a record with that number already exists, Summation prompts the user to either replace that record’s existing image information or leave its image information intact. The field normally used to determine a record’s unique number is either the BEGDOC# field (for the STDTABLE) or the DOCID field (for the ETABLE). This field can be changed via OPTIONS>DEFAULTS>IMAGING>COLUMN TO HOLD IMAGE TAG but it is not recommended. If there is an input template on the database’s record number field, then the @T value must conform to the template format.
Example: The case database has an input template restricting the BEGDOC# field to the format “AA000000” (i.e. alpha, alpha, numeric, numeric, numeric, numeric, numeric, numeric). A DII file with the following @T values is loaded: @T RT100556 @T 998113 The first line matches the template format and a new database record with a BEGDOC# value of “RT100556” would be created. The second line is incorrect, so no database record for this line would be created and an error message would appear on-screen and also be written to the error log. @D (Default Directory) Required for each DII record that has images or OCR to be loaded. The @D token designates the location where the image file(s) for a database record is stored. The data specified after the @D is loaded into the Default Directory (DEFDIR) field of the ImgInfo table. There are 3 different ways to denote the DEFDIR. 1. @I, which refers to the default IMAGES subfolder under the case directory. For example, for a mobile installation, if the case were SMITH V. JONES, “@I” would equal “C:\PROGRAM FILES\SUMMATION\CASEDATA\SMITH V. JONES\IMAGES." 2. The full path to the image file(s) location. A UNC, local, or mapped drive letter path is acceptable. For example: @D \SERVER1\IMAGES\SMITH V. JONES\VOLUME1\DISK1 @D C:\IMAGES\SMITH V. JONES\VOLUME1\DISK1 @D Z:\IMAGES\SMITH V. JONES\VOLUME1\DISK1 3. @V, which refers to the specific volume label of removable media. NOTE: Users of Summation LG/iBlaze can use UNC paths after the @D to specify a folder containing images. @L (Long Name Entry) Summation 5.21 Legacy Field. @L denotes the long name or description of the image file(s). The @L value is loaded into the LONGNAME field of the ImgInfo Table. This tag is obsolete and unnecessary on modern versions of Summation (1.0 and higher) as they support long image file names.
@C (Column to Link)
Optional token. @C is used to load data into specified fields in the user’s document database. This is a useful way to decrease the amount of data entry required for the database users. It is meant for use when the same value is repeated for a group of documents, such as documents that all have the same box number or author. It is not meant to replace regular data entry. For this...