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
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014
skos:broadMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

28,131 concepts found, displaying 2,661 to 2,680.First130131132133134135136137Last
Id Label Status Status Modified Notation
DE2317302 Dorumer Moor Quick edit Valid 2018-01-19 DE2317302
DE2317331 Extensivweiden nördlich Langen Quick edit Valid 2018-01-19 DE2317331
DE2320331 Westerberge bei Rahden Quick edit Valid 2018-01-19 DE2320331
DE2320332 Osteschleifen zwischen Kranenburg und Nieder-Ochtenhausen Quick edit Valid 2018-01-19 DE2320332
DE2322301 Schwingetal Quick edit Valid 2018-01-19 DE2322301
DE2322331 Wasserkruger Moor und Willes Heide Quick edit Valid 2018-01-19 DE2322331
DE2323392 Schleswig-Holsteinisches Elbästuar und angrenzende Flächen Quick edit Valid 2018-01-19 DE2323392
DE2323401 Unterelbe bis Wedel Quick edit Deprecated 2023-01-26 DE2323401
DE2323402 Unterelbe bis Wedel Quick edit Valid 2021-09-28 DE2323402
DE2324302 Schnaakenmoor Quick edit Valid 2018-01-19 DE2324302
DE2324303 Holmer Sandberge und Buttermoor Quick edit Valid 2018-01-19 DE2324303
DE2324304 NSG Tävsmoor / Haselauer Moor Quick edit Valid 2018-01-19 DE2324304
DE2325301 Ohmoor Quick edit Valid 2018-01-19 DE2325301
DE2326301 Wittmoor Quick edit Valid 2018-01-19 DE2326301
DE2326401 Hainesch/Iland Quick edit Valid 2018-01-19 DE2326401
DE2327301 Kammolchgebiet Höltigbaum / Stellmoor Quick edit Valid 2018-01-19 DE2327301
DE2327302 Stellmoorer Tunneltal/Höltigbaum Quick edit Valid 2018-01-19 DE2327302
DE2327351 Sieker Moor Quick edit Valid 2018-01-19 DE2327351
DE2328354 NSG Hahnheide Quick edit Valid 2018-01-19 DE2328354
DE2328355 Großensee, Mönchsteich, Stenzer Teich Quick edit Valid 2018-01-19 DE2328355
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?