Harvesting metadata from GeoModeller 3D geological mapping projects
Richard Lane
could be stored in a 3D mapping project to facilitate automated
harvesting of metadata.
The following are easy to obtain ...
** Map region (3D) and projection information
** Software version used to compile the map
** Date of the final compilation
** List of geological map units (i.e., legend entries)
It has been proposed that there be an option for each user to identify
him/herself when using the software. The proposed use of this
information would enable a list of interpreters/builders/mappers to be
extracted (i.e., those who impacted the stored data rather than those
who just viewed the results).
For each computational procedure that impacted the stored information
in the project, an entry to the project audit log would be created
with ...
** Name of procedure
** Date and time stamp
** Current user
** Settings used in the procedure
This information would enable a summary of the procedures used to
compile the map to be produced, at least the procedures involving
GeoModeller. There are plenty of important actions and decisions made
external to the program that would still need to be captured.
For each imported or created data item that is stored in the project,
the program would attach ...
** Date and time stamp
** Current user
** Option to attach a user attribute (such as a unique ID or link to
database source)
It is with respect to this last item that I would like to gain some
feedback. The intent is to provide a concise reference to the source
of each data item used to create the map, preferably one that can be
used to obtain a copy of the data, or to look at the history of the
observation, etc.
Some examples of the data items may help the thought process ...
** A formation name from a stratigraphic index.
** A relationship between 2 formations from a stratigraphic index.
** A set of points forming a boundary between 2 formations, obtained
from an existing digital 2D map.
** A bedding orientation measurement, obtained from an existing
digital 2D map.
** A portion of a surface topography grid supplied by a mapping
agency.
** Rock property distribution information from a corporate database.
** A portion of larger gravity or magnetic grids supplied by a
government survey.
** etc.
Are there well established methods for achieving the goal for this
link? For example, are there ways for an organisation to issue a
receipt when a user retrieves data from a data store, and for the
organisation to retain information that would describe the transaction
if the receipt was produced? And to reproduce the transaction on
demand?
Also, are there any other comments or suggestions with respect to the
proposed changes to GeoModeller regarding provenance and process audit
log tracking? Please distribute this email to anyone whom you think
may have a useful contribution to make on this subject.