Data Product Metadata Model

Scope

The Data Product Metadata Model (DPMM) describe the metadata elements of a Data Product. The metadata model is based on requirements defined by research projects (e.g. EcoPotential) as well as target stakeholder groups (e.g. LTER). The concept of ‘data product’ was added in order to allow a summarised description of a series of data. By this a fast overview on available data sources in a protected area can be created without a full description of each single dataset. This needs to be the logical second step and can not be replaced by the information on the data products.
The MD Model define the metadata elements describing the scope, content, methods and access of a group of datasets, which are grouped in a thematic data container, the data product. A linking of the information to the dataset MD is still an open task and will be implemented in the Version 1.1.

When applying the DPMM any data provider and site managers are enabled to:

  • provide as standardised overview description of their data
  • facilitate the sharing and discovery of data and information
  • enhance visibility and access to data from their observation facilities

Document history

The document describes the metadata elements of the current version 1.0 of the DPMM. The DPMM was developed within EcoPotential (H2020) project based on user needs.

Version: DPMM 1.0 / 2016-08-24


Figure: UML class diagram of the DPMM - CLICK to open full image


Terms and definitions

DATA PRODUCT (concept definition): a summarised description of a series of datasets by one 'thematic data container'. A ‘data product’ can be e.g. ‘Deposition data’, which contains a wide range of parameters and a long time series. Instead of describing each single dataset or parameter the ‘data product’ can be described as a whole. The related datasets (by its MD) can be linked to the data product.
By this a fast overview on available data sources in a protected area can be created without a full description of each single dataset. This should be the logical second step.

DATASET (concept definition): a single data file or a series of data files which are described with one dataset metadata record. The data object documented can either be a physical file or a data service (e.g. WFS, WMS). For datasets metadata as specified in the DEIMS community profile (link to INSPIRE and EML) or the INSPIRE MD SpecificationSpecfication need to be provided. Read more ...


A. IDENTIFICATION


1. DATA PRODUCT TITLE
Element 1.1 Title
Definition Provides a name of the data product that is being documented as is known within the community described in detail by following elements. Title is a characteristic and often unique and is the most informative element of a metadata record and usually with the highest priority as search engines go to this element.
Recommendation & Hints Title has to be concise and precisely describing the point. It should not contain unexplained acronyms or abbreviations. It is recommended a maximum length of 200 characters and keeping the similarity with the original title of the dataset in the sense of the ‘official naming’ established in the community. If the dataset is part of a larger project, it is recommended to indicate the Project at the end of the title, in brackets. In case of Project names, abbreviations are allowed, as long as the rest of the title follows the guidelines above and the abbreviation is spelled out immediately in the abstract.
The title should follow the following template:
SITE NAME _ DATA PRODUCT TYPE _ DATE RANGE (optional)
Format Text(255)
Multiplicity [1]
Required yes
Example DP_Zöbelboden_IP3_WetDeposition
Reference List n/a

2. RELATED SITE
Element 2.1 Site name
Definition Reference to the site (observation or experimentation facility) where the data were gathered.
Recommendation & Hints Please select the relevant sites from the list provided by DEIMS. The list provides all published sites in the DEIMS Site Registry. By typing the site name the system provides a list of research sites matching the query. If none available, please first document the site metadata using the editing form available and then return back to dataset metadata definition.
If the Data Product is defined as XML record, the field contains the link to the Site UUID.
Format Reference to [Content Type] SITE
Multiplicity [1..n]
Required yes
Example Zöbelboden LTER IM Master Site
Reference List Reference to [Content Type] SITE

A. GENERAL INFORMATION


3. DATA PRODUCT TYPE
Element 3.1 Data product type
Definition Reference to the thematic content of the data product.
Recommendation & Hints Classification of the data product according to data product types specified in the taxonomy. Please select a relevant category from the list, which describes the thematic context of the data product. If new categories are needed, please use the 'Provide feeback' link to post the request.
Format Reference to [Taxonomy] Data Product
Multiplicity [1]
Required yes
Example Meteorology
Reference List Reference to [Taxonomy] Data Product
  • Meteorology
  • |-- Air humidity
  • |-- Air pressure
  • |-- Air temperature
  • |-- Radiation
  • |---- Global radiation
  • |---- Photosynthetic active radiation (PAR)
  • ...
  • Air chemistry
  • |-- Carbon flux
  • ...

4. DATA PRODUCT ABSTRACT
Element 4.1 Abstract
Definition Short textual description of the data product documented as a summary of the resource.
Recommendation & Hints Please provide a short textual description on the scope, methods, policies applied to the data product. Please summarise the most important information in the first 100 words.
Format Text
Multiplicity [1]
Required yes
Example The data product contains monthly precipitation data collected at different weather stations at Zöbelboden. An automatic weather station is used to collect the data. The main variables are Air temperature at different heights and precipitaiton. The sampling intervall is every 15 minutes aggregated to 30 minutes values. An open data policy is applied to meteorological data.
The data product contains 10 different datasets from stations located in the study area. They can be accessed ...
Reference List n/a

5. PARAMETERS
Element 5.1 Parameters
Definition Description of the observed parameters and parameter groups for the data product. The parameter (or measure) is defined as property of the ecosystem or a ecosystem compartment which can be observed either by sensors or humans, e.g. pH, species number, radiation.
Recommendations & Hints Please indicate which parameters are provided by the data product. Please record every parameter. More than one entry is possible. The reference list is defined by the entries in EnvThes Measure and is frequently updated.
Format Reference [Taxonomy] Parameter
Multiplicity [0..n]
Required no
Example Precipitation, Air temperature, Atmospheric pressure
Reference List Reference [Taxonomy] Parameter based on EnvThes Measure
  • ...
  • Biodiversity
  • |- Biodiversity of animals
  • |- Biodiversity of microbes
  • |- Biodiversity of plants
  • |- Biodiversity, overal
  • |- Biodiversity, genetic
  • Biomass
  • |- Biomass, aquatic
  • |- Biomass, terrestrial
  • ...

6. KEYWORD SET
Element 6.1 EnvThes Keywords
Definition Provides a set of related keywords characterising the site derived from the controlled vocabulary implemented by EnvThes - thesaurus for long term ecological research, monitoring, experiments EnvThes and other environmentally related thesauri as Catalogue of Life, EUNIS Habitats and INSPIRE Spatial Data Themes.
Recommendations & Hints The keywords from the following groups can be selected:

The field provides an autocomplete function, which allows to select the values from the list. Begin typing a keyword. Select the one that most resembles the concept you want. You may add as many keywords as you need. The current version of EnvThes is cached in DEIMS. Therefore minor differences between the current version on the webserver and in DEIMS can occur. Updates of EnvThes in DEIMS are done automatically including updates of concepts.

Format Reference [Taxonomy] LTER Controlled Vocabulary
Multiplicity [0..n]
Required no
Example
  • Meteorology
  • Mixed forest
  • microclimate
  • Mountain forest
  • ecosystem ecology
  • rainfall chemical analysis
  • LTER Site
  • Reference List EnvThes captued in [Taxonomy] LTER Controlled Vocabulary

    C. DATA RESOLUTION

    This section describes the temporal and spatial resolution in which the data were gathered. The information should provide information to the user on how the data were gathered.


    7. DATA PRODUCT TEMPORAL EXTENT
    Element 7.1 From date
    7.2 To date
    Definition Defines the time period covered by the content of the data product (and the related datasets). This period may be expressed as a time (an individual date) or date ranges (interval of dates/From-To) or a mix of individual and interval dates.
    Recommendations & Hints Please provide the most appropriate range for the data collected. If the collection is still going on, please leave the to date blank.
    Format Date
    Multiplicity [1]
    Required yes
    Example 7.1 From date: 01-01-1991
    7.2 To date: 31-12-2013
    Reference List n/a

    8. TEMPORAL RESOLUTION
    Element 8.1 Temporal resolution
    Definition Description of the temporal resolution of the data. This describes the update frequency of the data, e.g. weekly or only one observation.
    Recommendations & Hints Please select the appropriate value from the list. If there are deviations or important issues to be mentioned, please describe that in addition in the abstract.
    Format Reference [Taxonomy] Temporal Resolution (Data Products)
    Multiplicity [1]
    Required yes
    Example minutes
    Reference List Reference [Taxonomy] Temporal Resolution (Data Products)
    • N/A
    • other temporal resolution
    • single measurement
    • less than seconds
    • seconds
    • minutes
    • hourly
    • half daily
    • daily
    • weekly
    • bi-weekly
    • monthly
    • bi-monthly
    • half yearly
    • yearly
    • bi-annual
    • every 2-5 years
    • ...

    9. SPATIAL RESOLUTION
    Element 9.1 Spatial resolution
    Definition Description of the spatial resolution of the data. This describes the spatial design for the data collection, e.g. area covering observations or grid points.
    Recommendations & Hints Please select the appropriate value from the list. If there are deviations or important issues to be mentioned, please describe that in addition in the abstract.
    Format Reference [Taxonomy] Spatial Resolution (Data Products)
    Multiplicity [1]
    Required yes
    Example minutes
    Reference List Reference [Taxonomy] Spatial Resolution (Data Products)
    • N/A
    • single point
    • transect sampling horizontal
    • transect sampling vertical
    • regular sampling
    • random sampling
    • stratified random sampling
    • full area coverage
    • catchment
    • plot
    • no spatial design
    • _unknown

    D. AVAILABILITY

    This section describes metadata elements which provide an overview on the availability of the data. It also could include a link to an online ressource locator providing either specific datasets or further informaton.


    10. DATA PRODUCT ONLINE DISTRIBUTION
    Element(s) Web adress title
    Web adress URL
    Definition Web address is the "navigation section" of a metadata record pointing users to the location (URL) where the datasets grouped in he data product can be retrieved directly, or provides information about how to acquire a datasets.
    Recommendations & Hints Setting up the correct resource locators is important for the connection between the data and the services that provide access to them or for providing additional information concerning the resource. If Web address for dataset is available, the Dataset Locator shall be a valid URL providing one of the following: a link to a web page with further instructions; a link to a web service capabilities document; a link to a client application (web data portal) that directly accesses dataset. If a dataset is available offline, it may be uploaded into the system and made online available with access and use constraints and IPR defined previously.
    Format Web address title Text(255)
    Web address URL URL
    Multiplicity [0..1]
    Required no
    Example Web address title: LTER Europe Sensor Observation Service (SOS)
    Web address URL: http://sp7.irea.cnr.it/tomcat/envsos/sos?REQUEST=getcapabilities&service...
    Reference List n/a

    11. DATA PRODUCT FORMAT
    Element 11.1 Data digitally available
    Definition Indication if the data are available in digital format.
    Recommendations & Hints Please indicate, if the data are available in digital format.
    Format Reference
    Multiplicity [1]
    Required yes
    Example yes
    Reference List
    • n/a
    • yes
    • no

    12. DATA PRODUCT POLICY
    Element 11.1 Data openly available
    Definition Indication if the data are available as open data.
    Recommendations & Hints Please indicate, if the data are available as open data.
    Format Reference
    Multiplicity [1]
    Required yes
    Example yes
    Reference List
    • n/a
    • yes
    • no

    13. DATA AVAILABILITY
    Element 13.1 Data available for EcoPotential
    Definition Indication if the data are freely available within the EcoPotential H2020 project.
    Recommendations & Hints Please indicate, if the data are freely available within the EcoPotential H2020 project.
    Format Reference
    Multiplicity [1]
    Required yes
    Example yes
    Reference List
    • n/a
    • yes
    • no

    E. CONTACT

    This section provides information on contact points. Note: the inclusion of MD Creator and MD Edit Date needs to be discussed for the next release of the DP MD model.


    14. DATASET CREATOR & CONTACT POINTS
    Element(s) 14.1 Responsible party
    Definition Provides the full name of person(s), who created the dataset or who serve as contact points.
    Recommendations & Hints By typing the name of a person, the system provides a list of people matching the query. If none available, it's strongly recommended to first create a person metadata using the editing form available and then return back to dataset metadata definition.
    Format Reference [Content Type] Person
    Multiplicity [1..n]
    Required yes
    Example Kobler, Johannes
    Reference List Reference [Content Type] Person

    General notes

    For each data product a MD record is created and referenced to the site/protected area. In a later phase dataset MD can also be linked to the data product.