Skip to content

Basic metadata

Peter Desmet edited this page Feb 8, 2021 · 8 revisions

Terms

Term Status
Shortname Required
Title Required
Publishing organization Required
Type Required
Subtype Share if available
Metadata language Required
Data language Required
Update frequency Required
Data license Required
Description Required

Details

Shortname

The shortname is used to reference the dataset on the IPT or GitHub (it is part of the URL). It should be lowercase, hyphenated and stable. It cannot be changed once the dataset is created. For occurrence datasets the shortname generally starts with the name of the originating database, so datasets of the same origin appear together (meetnetten-, vis-). The shortname always ends with the dataset type (-occurrences or -checklist). The use of -events has been discontinued, because datasets might change format (Occurrence Core vs Event Core).

watervogels-occurrences                  # db + occurrences
vis-inland-occurrences                   # db + subset + occurrences
meetnetten-amfibieen-fuiken-occurrences  # db + subset + subset + occurrences
alien-fishes-checklist                   # topic + checklist

Title

The title is a human readable name for the dataset, succinctly describing its scope and with capitalization where necessary. It always ends with the geographic scope (... in Flanders, Belgium). For occurrence datasets the title generally starts with the name of the originating database, followed by space hyphen space, so datasets of the same origin appear together (Meetnetten.be - ..., VIS - ..., Waarnemingen.be - ...).

Watervogels - Wintering waterbirds in Flanders, Belgium         # watervogels-occurrences
VIS - Fishes in inland waters in Flanders, Belgium              # vis-inland-occurrences
Meetnetten.be - Fyke counts for Amphibia in Flanders, Belgium   # meetnetten-amfibieen-fuiken-occurrences
Checklist of non-native freshwater fishes in Flanders, Belgium  # alien-fishes-checklist

Publishing organization

Is set by the IPT when registering the dataset and cannot be changed later.

Type

Is set by the IPT when creating a dataset and cannot be changed later.

Occurrence
Sampling event
Checklist

Subtype

A dropdown menu:

Observation         # For INBO occurrence datasets (monitoring, citizen science, machine observations)
Inventory thematic  # For invasive species checklists
Inventory regional  # For regional checklists

Metadata language

English

Data language

English

Update frequency

A dropdown menu:

Not planned # For datasets that are no longer updated
As needed   # For datasets with irregular updates
Annually    # Or similar, for ongoing monitoring

Data license

All INBO datasets are published under Creative Commons Zero (see data policy). For other publishing organizations, the license should be discussed with the data owner, but note that GBIF only allows three licenses.

Public domain (CC0 1.0)

Description

The description acts as the abstract of the dataset. It is often the only descriptive metadata that appears on metadata portals, such as PURE or the Flemish Open Data Portal and should allow the user to understand the origin, scope, and terms of use.

Paragraph 1 Required

Note: this guidelines is not yet completed. Mention data paper reference (+ DOI) + end with something like: "Issues with the dataset can be reported at https://github.com/trias-project/alien-fishes-checklist"

Checklist example:

The Checklist of non-native freshwater fishes in Flanders, Belgium is a species checklist dataset published by the Research Institute for Nature and Forest (INBO). It contains information on 23 alien fish species occurring in Flemish natural and semi-natural waterbodies, detected in sampling between 1992 and 2006. This species checklist was assessed within the framework of the Freshwater Fish Monitoring Network by Verreycken et al. (2007) and reassessed for Verreycken et al. (2018). Here it is published as a standardized Darwin Core Archive and includes for each species: the scientific name, kingdom, and stable taxon ID (in the taxon core), the Dutch and English vernacular name (in the vernacular names extension), the year of first introduction and last assessment in Flanders (given as a year range in the event date in the distribution extension), coarse habitat information (in the species profile extension) and the pathway(s) of introduction, native range(s), and invasion stage in Flanders (in the description extension). The dataset can be used for researching and managing aquatic invasions or compiling regional and national registries of alien species. Issues with the dataset can be reported at https://github.com/trias-project/alien-fishes

Paragraph 2 Share if available

This paragraph contains information on withheld data, data generalizations and recommendations on data use (e.g. caveats for species modelling):

Examples:

The following information is not included in the dataset and available upon request: outliers, temperature, speed, accelerometer data, GPS metadata (fix time, number of satellites used, vertical accuracy), bird biometrics data measured during tagging (bill length, bill depth, tarsus length, wing length, body mass), life history data (day of ringing, age, resightings by volunteers), as well as growth data of chicks.

Generalized and/or withheld information: location information is generalized to 5 x 5 km² Universal Transverse Mercator (UTM) grid cells. Observer name, exact XY-coordinates, toponyms, and photographs are not included in the published dataset, but are known in the source database.

Captured bullfrogs were almost always removed from the environment and humanely killed, while the other occurrences are recorded bycatch, which were released upon catch (see bibliography for detailed descriptions of the methods). Therefore, caution is advised when using these data for trend analysis, distribution range calculation, or other.

Paragraph 3 Required

This paragraph contains a standard phrasing (that can be copy/pasted) regarding our open data approach:

For INBO datasets:

We have released this dataset to the public domain under a Creative Commons Zero waiver. We would appreciate it if you follow the INBO norms for data use (https://www.inbo.be/en/norms-data-use) when using the data. If you have any questions regarding this dataset, don't hesitate to contact us via the contact information provided in the metadata or via [email protected].

For TrIAS datasets:

We have released this dataset to the public domain under a Creative Commons Zero waiver. We would appreciate it if you follow the GBIF citation guidelines (https://www.gbif.org/citation-guidelines) when using the data. If you have any questions regarding this dataset, don't hesitate to contact us via the contact information provided in the metadata or via https://twitter.com/trias_project.

Paragraph 4 Share if available

This paragraph includes an acknowledgement of the funding agency.

Examples:

The publication of this dataset was supported by the INBO as part of the Flemish contribution to LifeWatch.

The bird tracking network generating these data is supported by the INBO and VLIZ as part of the Flemish contribution to LifeWatch.