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,521 to 10,540.First523524525526527528529530Last
Id Label Status Status Modified Notation
16065054 Oldisleben Quick edit Valid 2009-01-01 16065054
16065056 Reinsdorf Quick edit Valid 2009-01-01 16065056
16065057 Ringleben Quick edit Valid 2009-01-01 16065057
16065058 Rockstedt Quick edit Valid 2009-01-01 16065058
16065061 Roßleben, Stadt Quick edit Valid 2009-01-01 16065061
16065062 Rottleben Quick edit Valid 2009-01-01 16065062
16065066 Seega Quick edit Valid 2009-01-01 16065066
16065067 Sondershausen, Stadt Quick edit Valid 2009-01-01 16065067
16065068 Steinthaleben Quick edit Valid 2009-01-01 16065068
16065072 Thüringenhausen Quick edit Valid 2009-01-01 16065072
16065074 Topfstedt Quick edit Valid 2009-01-01 16065074
16065075 Trebra Quick edit Valid 2009-01-01 16065075
16065076 Voigtstedt Quick edit Valid 2009-01-01 16065076
16065077 Wasserthaleben Quick edit Valid 2009-01-01 16065077
16065079 Westgreußen Quick edit Valid 2009-01-01 16065079
16065081 Wiehe, Stadt Quick edit Valid 2009-01-01 16065081
16065082 Wolferschwenda Quick edit Valid 2009-01-01 16065082
16065084 Großenehrich, Stadt Quick edit Valid 2009-01-01 16065084
16066001 Altersbach Quick edit Valid 2009-01-01 16066001
16066002 Aschenhausen Quick edit Valid 2009-01-01 16066002
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?