Talk:Data model

The data model (old version)

The great variety of parameters and methods used in environmental and geological research are major obstacles to the use of data sets in an integrative system. The challenge of managing this heterogenic and dynamic data was met through a highly flexible data model consisting of a relational data structure in combination with specialized server software generating an object-oriented view of the data.

The simplified data structure is used as the entrance level and allows users to access all levels, tables and tools by selecting the required field. The structure follows the processing steps for analytical data in principle. Different institutes/projects (PROJECT) carry out expeditions/investigations (CAMPAIGN) for sampling or measurements. At a number of locations (SITE), different samples may be taken or measurements made (EVENT). At distinct points/intervals, the medium to be investigated (e.g. sediment, water or ice) is subsampled or measured for different requirements. Information about the sampling procedure and the sampling material can be stored at the SAMPLE level. From each sample, one or more analytical data points will be derived. They can be found on the DATA level with the accompanied meta-information necessary for its understanding.

Within the relational structure of the system lists including standardized meta-information are connected to the main data fields (e.g. reference, method, parameter). The parameters are gathered into parameter groups for a better overview. Data can be defined as primary (raw data), secondary ("real" analytical data) and tertiary data as calculated from the secondary data. Data types can be numerical, textual or pictures. The combination of the DATA, 'Parameter' and 'Method' fields is the essential part of the model, which allows the definition and storage of new, unique parameters by the user at any time. The technical data quality can be checked by parameter specific validation routines. All data sets are copyright protected within a hierarchical protection system. The middleware allows the user to retrieve individual configured data sets, e.g. restricted by time and space.