You are here:
Eionet
Data Dictionary
Edit vocabulary

Edit vocabulary

Folder Mandatory
Identifier Mandatory
Label Mandatory
Base URI Optional
Registration status Mandatory
Type Mandatory Common
Numeric concept identifiers Mandatory
Optional
Definition Optional
Version Optional
Source Optional
License Optional
 

Bound elements for concepts

Element Type Status
adms:status Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
01 Oct 2015
dct:isReplacedBy Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
dct:replaces Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
hasIdentifierScheme Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
22 Nov 2024
hasRelatedZone Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Feb 2016
hasSpecialisedZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
03 Nov 2015
hasZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
18 Oct 2016
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014
skos:exactMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

276,424 concepts found, displaying 1,541 to 1,560.First7475767778798081Last
Id Label Status Status Modified Notation
eionetGroundWaterBodyCode.DEGB_VM-1-2 VEREINIGTE MULDE Quick edit Deprecated - retired 2021-06-17 DEGB_VM-1-2
eionetGroundWaterBodyCode.DEGB_VM-1-3 SCHWARZBACH Quick edit Deprecated - retired 2021-06-17 DEGB_VM-1-3
eionetGroundWaterBodyCode.DEGB_VM-2-1 MULDETAL Quick edit Deprecated - retired 2021-06-17 DEGB_VM-2-1
eionetGroundWaterBodyCode.DEGB_VM-2-3 MORAENENLANDSCHAFT DUEBENER HEIDE Quick edit Deprecated - retired 2021-06-17 DEGB_VM-2-3
eionetGroundWaterBodyCode.DEGB_VM-2-4 BITTERFELDER QUARTAERPLATTE Quick edit Deprecated - retired 2021-06-17 DEGB_VM-2-4
eionetGroundWaterBodyCode.DEGB_WP_KO_2 DARSS ZINGST Quick edit Deprecated - retired 2021-06-17 DEGB_WP_KO_2
eionetGroundWaterBodyCode.DEGB_WP_KO_4 STRALSUND Quick edit Deprecated - retired 2021-06-17 DEGB_WP_KO_4
eionetGroundWaterBodyCode.DEGB_WP_KO_6 USEDOM MITTE Quick edit Deprecated - retired 2021-06-17 DEGB_WP_KO_6
eionetGroundWaterBodyCode.DEGB_WP_KO_9 MITTELRUGEN Quick edit Deprecated - retired 2021-06-17 DEGB_WP_KO_9
eionetGroundWaterBodyCode.DEGB_WP_KW_2 WALLENSTEINGRABEN Quick edit Deprecated - retired 2021-06-17 DEGB_WP_KW_2
eionetGroundWaterBodyCode.DEGB_WP_PT_1 OSTPEENE Quick edit Deprecated - retired 2021-06-17 DEGB_WP_PT_1
eionetGroundWaterBodyCode.DEGB_WP_PT_3 MITTLERE PEENE Quick edit Deprecated - retired 2021-06-17 DEGB_WP_PT_3
eionetGroundWaterBodyCode.DEGB_WP_PT_6 PEENE Quick edit Deprecated - retired 2021-06-17 DEGB_WP_PT_6
eionetGroundWaterBodyCode.DEGB_WP_TO_1 TOLLENSESEE Quick edit Deprecated - retired 2021-06-17 DEGB_WP_TO_1
eionetGroundWaterBodyCode.DEGB_WP_TO_3 AUGRABEN Quick edit Deprecated - retired 2021-06-17 DEGB_WP_TO_3
eionetGroundWaterBodyCode.DEGB_WP_TO_4 TOLLENSE Quick edit Deprecated - retired 2021-06-17 DEGB_WP_TO_4
eionetGroundWaterBodyCode.DEGB_WP_WA_2 WARNOW GOWE Quick edit Deprecated - retired 2021-06-17 DEGB_WP_WA_2
eionetGroundWaterBodyCode.DEGB_WP_WA_3 RADEBACH Quick edit Deprecated - retired 2021-06-17 DEGB_WP_WA_3
eionetGroundWaterBodyCode.DEGB_WP_WA_6 NEBEL Quick edit Deprecated - retired 2021-06-17 DEGB_WP_WA_6
eionetGroundWaterBodyCode.DEGB_WP_WA_7 SEEBACH Quick edit Deprecated - retired 2021-06-17 DEGB_WP_WA_7
CSV Import

The CSV file should contain a header row for element names and data rows for concepts.
It is strongly recommended to use an exported CSV file as a template for bulk editing. Columns and rows can be added to or deleted from the template file.
A concept can be ignored by prepending a double-slash '//' to the concept row in the CSV
    Notes:
  • If the header row contains unknown elements the import will aborted and data will be rolled back
  • Erroneous concept rows are ignored, valid data rows are still imported
  • Successful import cannot be undone (unless "undo checkout" is performed)
  • If a concept with the same identifier already exists in the vocabulary it will be overwritten
  • "Purge Vocabulary" option deletes all the vocabulary concepts before import
Note
  • With this operation, contents of RDF file will be imported into vocabulary folder.
  • Only a working copy can be updated with a RDF file upload.
  • If user select "Purge Per Predicate" option. All seen predicates will be removed from vocabulary.
  • If user select "Purge All Vocabulary Data" option. All data will be removed from vocabulary.
  • Once import is successful, operation cannot be undone. If an error occurs during import, then all data will be rolled back.
In this case, existing vocabulary information will be updated with information from imported concepts.
In this case, predicates of existing concepts will be replaced with the imported predicates.
In this case, all existing concepts will be removed and the imported concepts will be added.
In this case, all imported concepts will be removed from the vocabulary.
How to handle missing concepts?