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
owl:sameAs Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013
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 (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

4,043 concepts found, displaying 681 to 700.First3132333435363738Last
Id Label Status Status Modified Notation
DE40 Brandenburg Quick edit Valid 2013-09-25 DE40
DE401 Brandenburg an der Havel, Kreisfreie Stadt Quick edit Valid 2013-09-25 DE401
DE402 Cottbus, Kreisfreie Stadt Quick edit Valid 2013-09-25 DE402
DE403 Frankfurt (Oder), Kreisfreie Stadt Quick edit Valid 2013-09-25 DE403
DE404 Potsdam, Kreisfreie Stadt Quick edit Valid 2013-09-25 DE404
DE405 Barnim Quick edit Valid 2013-09-25 DE405
DE406 Dahme-Spreewald Quick edit Valid 2013-09-25 DE406
DE407 Elbe-Elster Quick edit Valid 2013-09-25 DE407
DE408 Havelland Quick edit Valid 2013-09-25 DE408
DE409 Märkisch-Oderland Quick edit Valid 2013-09-25 DE409
DE40A Oberhavel Quick edit Valid 2013-09-25 DE40A
DE40B Oberspreewald-Lausitz Quick edit Valid 2013-09-25 DE40B
DE40C Oder-Spree Quick edit Valid 2013-09-25 DE40C
DE40D Ostprignitz-Ruppin Quick edit Valid 2013-09-25 DE40D
DE40E Potsdam-Mittelmark Quick edit Valid 2013-09-25 DE40E
DE40F Prignitz Quick edit Valid 2013-09-25 DE40F
DE40G Spree-Neiße Quick edit Valid 2013-09-25 DE40G
DE40H Teltow-Fläming Quick edit Valid 2013-09-25 DE40H
DE40I Uckermark Quick edit Valid 2013-09-25 DE40I
DE41 Brandenburg - Nordost (NUTS 2006) Quick edit Valid 2013-09-25 DE41
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?