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,510 concepts found, displaying 3,441 to 3,460.First169170171172173174175176Last
Id Label Status Status Modified Notation
DE3411331 Pottebruch und Umgebung Quick edit Valid 2018-01-19 DE3411331
DE3411332 Swatte Poele Quick edit Valid 2018-01-19 DE3411332
DE3414331 Dammer Berge Quick edit Valid 2018-01-19 DE3414331
DE3415301 Dümmer Quick edit Valid 2018-01-19 DE3415301
DE3415401 Dümmer Quick edit Valid 2018-01-19 DE3415401
DE3416301 Rehdener Geestmoor Quick edit Valid 2018-01-19 DE3416301
DE3416302 Oppenweher Moor Quick edit Valid 2018-01-19 DE3416302
DE3417301 Oppenweher Moor Quick edit Valid 2018-01-19 DE3417301
DE3417471 Vogelschutzgebiet Oppenweher Moor Quick edit Valid 2018-01-19 DE3417471
DE3418301 Renzeler Moor Quick edit Valid 2018-01-19 DE3418301
DE3418401 Diepholzer Moorniederung Quick edit Valid 2018-01-19 DE3418401
DE3419401 Kuppendorfer Böhrde Quick edit Valid 2018-01-19 DE3419401
DE3420331 Steinhuder Meer (mit Randbereichen) Quick edit Valid 2018-01-19 DE3420331
DE3420401 Wesertalaue bei Landesbergen Quick edit Valid 2018-01-19 DE3420401
DE3421301 Rehburger Moor Quick edit Valid 2018-01-19 DE3421301
DE3421331 Häfern Quick edit Valid 2018-01-19 DE3421331
DE3423331 Helstorfer, Otternhagener und Schwarzes Moor Quick edit Valid 2018-01-19 DE3423331
DE3424301 Bissendorfer Moor Quick edit Valid 2018-01-19 DE3424301
DE3424331 Quellwald bei Bennemühlen Quick edit Valid 2018-01-19 DE3424331
DE3425301 Trunnenmoor Quick edit Valid 2018-01-19 DE3425301
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?