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
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 921 to 940.First4344454647484950Last
Id Label Status Status Modified Notation
DEB1A Rhein-Lahn-Kreis Quick edit Valid 2013-09-25 DEB1A
DEB1B Westerwaldkreis Quick edit Valid 2013-09-25 DEB1B
DEB1C Cochem-Zell Quick edit Valid 2018-02-14 DEB1C
DEB1D Rhein-Hunsrück-Kreis Quick edit Valid 2018-02-14 DEB1D
DEB2 Trier Quick edit Valid 2013-09-25 DEB2
DEB21 Trier, Kreisfreie Stadt Quick edit Valid 2013-09-25 DEB21
DEB22 Bernkastel-Wittlich Quick edit Valid 2013-09-25 DEB22
DEB23 Eifelkreis Bitburg-Prüm Quick edit Valid 2013-09-25 DEB23
DEB24 Vulkaneifel Quick edit Valid 2013-09-25 DEB24
DEB25 Trier-Saarburg Quick edit Valid 2013-09-25 DEB25
DEB3 Rheinhessen-Pfalz Quick edit Valid 2013-09-25 DEB3
DEB31 Frankenthal (Pfalz), Kreisfreie Stadt Quick edit Valid 2013-09-25 DEB31
DEB32 Kaiserslautern, Kreisfreie Stadt Quick edit Valid 2013-09-25 DEB32
DEB33 Landau in der Pfalz, Kreisfreie Stadt Quick edit Valid 2013-09-25 DEB33
DEB34 Ludwigshafen am Rhein, Kreisfreie Stadt Quick edit Valid 2013-09-25 DEB34
DEB35 Mainz, Kreisfreie Stadt Quick edit Valid 2013-09-25 DEB35
DEB36 Neustadt an der Weinstraße, Kreisfreie Stadt Quick edit Valid 2013-09-25 DEB36
DEB37 Pirmasens, Kreisfreie Stadt Quick edit Valid 2013-09-25 DEB37
DEB38 Speyer, Kreisfreie Stadt Quick edit Valid 2013-09-25 DEB38
DEB39 Worms, Kreisfreie Stadt Quick edit Valid 2013-09-25 DEB39
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?