Administration
This section provides information on the considerations necessary when setting up a new profile to be used with the Logging Integrator.
Setup a new profile
Collection vs. Storage
The Geobank Database is structured in such a way as to best store data. The way the field geologists want to see the data when they are capturing it is often different to this. So before setting-up a new logging profile, first plan how you want the structure to be different for the people logging the data. This involves:
-
Deciding on logging-oriented table and field names to use
-
Deciding which types of data are represented in more than one table in the Geobank database, but should be collected together.
-
Where Geobank database tables are combined, identify one column for each of the tables which if no value is logged, it means there is no need to load a row into the underlying Geobank database table.
-
Decide on which column names, relating to Collar or Sample attributes, can be planned prior to logging. This will then allow these values to be pushed out into the logging profiles, and guide people doing the logging to avoid mistakes in IDs or planned usage (such as certain sample_ids pre-allocated to be field duplicated).
One example is GB_SITE and GB_SITE_SURVEY, where the collar attributes and location are stored in separate tables: From a logging perspective it makes sense to collect a collar's attributes and drilled location in a single table.
Another example is there may be multiple interval tables in the database such as lithology and mineralisation, but when collecting you want to collect all these interval attributes in a single Geology table.
Step 2 - Create then Review/Edit Metadata
Step 3 - Create the Geobank For Field Teams logging profile