Jump to content

QDI Mapping file structure

From QESTonline
Revision as of 01:20, 20 July 2007 by David.murphy (talk | contribs) (Categorised)

QDI Mapping file for QESTLab concrete dockets:

Anything preceded by a '#' is a comment, the first few options are as follows:

TABLENAME:DocumentConcreteDockets
SYSTEM:QESTLAB
DATAFILE:TK*.in
TRIMLEADINGZEROS:TRUE

In order these suggest:

  • This applies to the DocumentConcreteDockets table
  • This mapping file applies to the QESTLab system
  • It will read in any files which have a filename of the structure TK*.in where the '*' is a wildcard standing for any string of characters.
  • Leading zeros will be trimmed from values.

The rest of the file is structured as follows:

fieldName,offset,length,type,key,default
Table 1
Field Meaning Values
fieldName This is the field in the given table that the values will be mapped to. Will be a string relating to a column name.
offset The character offset at which the value will be found in the data file. Will be a number.
length The acceptable length of the field in the data file. Will be a number.
type The field type. "N" - numeric, "D"/"T" - Date/Time, "S" - String
key Denotes whether or not this is the primary key of the table. "T" - True, "F" - False
default Default field value. Depends on the field type.

See Also

For Spectra QEST staff, the file:
\\adls0003\Documents\Spectra QEST\Software\Procedures\IQ0023 QDI Mapping File Specification.htm
contains a partially complete list of the available options/settings for QDI Mapping Files.