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,961 to 2,980.First145146147148149150151152Last
Id Label Status Status Modified Notation
DE2723331 Wümmeniederung Quick edit Valid 2018-01-19 DE2723331
DE2723401 Moore bei Sittensen Quick edit Valid 2018-01-19 DE2723401
DE2724331 Kauers Wittmoor Quick edit Valid 2018-01-19 DE2724331
DE2725301 Lüneburger Heide Quick edit Valid 2018-01-19 DE2725301
DE2726331 Garlstorfer und Toppenstedter Wald Quick edit Valid 2018-01-19 DE2726331
DE2727331 Laubwälder am Einemhof und Kranichmoor Quick edit Valid 2018-01-19 DE2727331
DE2727332 Mausohr-Wochenstubengebiet Elbeeinzugsgebiet Quick edit Valid 2018-01-19 DE2727332
DE2732371 Rögnitzniederung Quick edit Valid 2018-01-19 DE2732371
DE2732473 Mecklenburgisches Elbetal Quick edit Valid 2018-01-19 DE2732473
DE2733301 Lübtheener Heide und Trebser Moor Quick edit Valid 2018-01-19 DE2733301
DE2733401 Lübtheener Heide Quick edit Valid 2018-01-19 DE2733401
DE2734401 Feldmark Eldena bei Grabow Quick edit Valid 2018-01-19 DE2734401
DE2735301 Alte Elde zwischen Wanzlitz und Krohn Quick edit Valid 2018-01-19 DE2735301
DE2736301 Löcknitz-Oberlauf und angrenzende Wälder (MV) Quick edit Valid 2018-01-19 DE2736301
DE2736471 Feldmark Stolpe - Karrenzin - Dambeck - Werle Quick edit Valid 2018-01-19 DE2736471
DE2737301 Gülitzer Kohlegruben Quick edit Valid 2018-01-19 DE2737301
DE2737302 Ruhner Berge Quick edit Valid 2018-01-19 DE2737302
DE2738301 Hainholz an der Stepenitz Quick edit Valid 2018-01-19 DE2738301
DE2738302 Stepenitz Quick edit Valid 2018-01-19 DE2738302
DE2738421 Agrarlandschaft Prignitz-Stepenitz Quick edit Valid 2018-01-19 DE2738421
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?