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:broadMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

11,204 concepts found, displaying 10,801 to 10,820.First537538539540541542543544Last
Id Label Status Status Modified Notation
16070055 Wolfsberg Quick edit Valid 2009-01-01 16070055
16070056 Ilmtal Quick edit Valid 2009-01-01 16070056
16071001 Apolda, Stadt Quick edit Valid 2009-01-01 16071001
16071002 Auerstedt Quick edit Valid 2009-01-01 16071002
16071003 Bad Berka, Stadt Quick edit Valid 2009-01-01 16071003
16071004 Bad Sulza, Stadt Quick edit Valid 2009-01-01 16071004
16071005 Ballstedt Quick edit Valid 2009-01-01 16071005
16071006 Bechstedtstraß Quick edit Valid 2009-01-01 16071006
16071007 Berlstedt Quick edit Valid 2009-01-01 16071007
16071008 Blankenhain, Stadt Quick edit Valid 2009-01-01 16071008
16071009 Buchfart Quick edit Valid 2009-01-01 16071009
16071011 Buttelstedt, Stadt Quick edit Valid 2009-01-01 16071011
16071012 Daasdorf a. Berge Quick edit Valid 2009-01-01 16071012
16071013 Döbritschen Quick edit Valid 2009-01-01 16071013
16071015 Eberstedt Quick edit Valid 2009-01-01 16071015
16071017 Ettersburg Quick edit Valid 2009-01-01 16071017
16071018 Flurstedt Quick edit Valid 2009-01-01 16071018
16071019 Frankendorf Quick edit Valid 2009-01-01 16071019
16071021 Gebstedt Quick edit Valid 2009-01-01 16071021
16071022 Großheringen Quick edit Valid 2009-01-01 16071022
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?