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 11,181 to 11,200.First554555556557558559560561Last
Id Label Status Status Modified Notation
16077019 Jückelberg Quick edit Valid 2009-01-01 16077019
16077022 Kriebitzsch Quick edit Valid 2009-01-01 16077022
16077023 Langenleuba-Niederhain Quick edit Valid 2009-01-01 16077023
16077026 Löbichau Quick edit Valid 2009-01-01 16077026
16077027 Lödla Quick edit Valid 2009-01-01 16077027
16077028 Lucka, Stadt Quick edit Valid 2009-01-01 16077028
16077029 Lumpzig Quick edit Valid 2009-01-01 16077029
16077031 Mehna Quick edit Valid 2009-01-01 16077031
16077032 Meuselwitz, Stadt Quick edit Valid 2009-01-01 16077032
16077034 Monstab Quick edit Valid 2009-01-01 16077034
16077036 Nobitz Quick edit Valid 2009-01-01 16077036
16077037 Nöbdenitz Quick edit Valid 2009-01-01 16077037
16077039 Ponitz Quick edit Valid 2009-01-01 16077039
16077041 Posterstein Quick edit Valid 2009-01-01 16077041
16077042 Rositz Quick edit Valid 2009-01-01 16077042
16077043 Schmölln, Stadt Quick edit Valid 2009-01-01 16077043
16077044 Starkenberg Quick edit Valid 2009-01-01 16077044
16077047 Thonhausen Quick edit Valid 2009-01-01 16077047
16077048 Treben Quick edit Valid 2009-01-01 16077048
16077049 Vollmershain Quick edit Valid 2009-01-01 16077049
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?