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 561 to 580.First2526272829303132Last
Id Label Status Status Modified Notation
DE1BA Baden Quick edit Valid 2013-09-25 DE1BA
DE1WU Württemberg Quick edit Valid 2013-09-25 DE1WU
DE1_E Baden-Württemberg East Quick edit Valid 2013-09-25 DE1_E
DE1_N_W Baden-Württemberg North West Quick edit Valid 2013-09-25 DE1_N_W
DE1_S_W Baden-Württemberg South West Quick edit Valid 2013-09-25 DE1_S_W
DE2 Bayern Quick edit Valid 2013-09-25 DE2
DE21 Oberbayern Quick edit Valid 2013-09-25 DE21
DE211 Ingolstadt, Kreisfreie Stadt Quick edit Valid 2013-09-25 DE211
DE212 München, Kreisfreie Stadt Quick edit Valid 2013-09-25 DE212
DE213 Rosenheim, Kreisfreie Stadt Quick edit Valid 2013-09-25 DE213
DE214 Altötting Quick edit Valid 2013-09-25 DE214
DE215 Berchtesgadener Land Quick edit Valid 2013-09-25 DE215
DE216 Bad Tölz-Wolfratshausen Quick edit Valid 2013-09-25 DE216
DE217 Dachau Quick edit Valid 2013-09-25 DE217
DE218 Ebersberg Quick edit Valid 2013-09-25 DE218
DE219 Eichstätt Quick edit Valid 2013-09-25 DE219
DE21A Erding Quick edit Valid 2013-09-25 DE21A
DE21B Freising Quick edit Valid 2013-09-25 DE21B
DE21C Fürstenfeldbruck Quick edit Valid 2013-09-25 DE21C
DE21D Garmisch-Partenkirchen Quick edit Valid 2013-09-25 DE21D
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?