Designs
Designs (in Dbeute these were called Datasheets) are the prerequisites to a Vulcan database. They define the structure of a database. It enables you to define tables and fields that specify data properties, such as length, type and synonyms. The basis for a design can be derived from any source, such as a geologist's logging sheet or raw data files.
The following designs formats are used:
| File Name | Description |
|---|---|
| <env><dsn>.ilb |
Design library file (stores extra information, such as right justification, about the design) |
| <env>dd.ilb |
Index to library file (stores all of the core information about the designs as well as containing a list of all the design names). |
where
<env> = environment code,
<dsn> = design name,
dd = design definition.
The design information includes tables and records. Synonyms are stored in a separate, automatically created, design named <env><dsn>.syn for the synonym design and <env>dd.syn for the index to the synonym sheet, both of which contain the same synonym information for a design.
Headered template
The headered template design is an optimised Isis design that can be used for drillholes, samples, geotechnical and compositing information (not for design data). It consists of a single file:
| File Name | Description |
|---|---|
| <name>.dsf | Design file (stores all the information on the design) |
where <name> = design name. The design information includes tables, records, keys, synonyms, desurvey information, validation checks and the version of the headered data system used in the creation of the design.
Once a database has been created, the design information becomes part of the database (placed at the start of the database, hence the name headered). Any future access to the database will be via the database.
Note: The name may be changed when moving the design to another location.
ODBC design
The ODBC design is identical to a headered design. The only difference is that the design information includes a flag indicating the design is for use with external ODBC compliant databases such as Microsoft Access or Microsoft Excel. External ODBC compliant databases are accessed in Vulcan through a temporary database that contains a copy of all the Vulcan data in the external database. Work is performed on the copy and when finished written back to the external database.
Care must be taken when managing designs as any changes made to a design will not be reflected in previously created headered databases. For the databases to reflect the changes, the databases would need to be reloaded. However, please note that design changes will be reflected in library databases.
Vulcan panels that use a drop-down list of designs include all of the above design formats.
Vulcan controls a number of designs that cannot be redefined. These are:
.dgd and .dgd.isis (design data)
.rsv (reserve data)
.rin (reserve data)
.dsr (downhole desurveyed data)
.str (stratigraphic data).
Some examples of commonly used design names are GEO (for drilling, mostly coal), ASY (for drilling, mostly metals), CMP (for compositing), BHS (for blast holes), CHA (for channel samples).
