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,021 to 11,040.First548549550551552553554555Last
Id Label Status Status Modified Notation
16074108 Weißbach Quick edit Valid 2009-01-01 16074108
16074109 Weißenborn Quick edit Valid 2009-01-01 16074109
16074112 Wichmar Quick edit Valid 2009-01-01 16074112
16074113 Zimmern Quick edit Valid 2009-01-01 16074113
16074114 Zöllnitz Quick edit Valid 2009-01-01 16074114
16074116 Schkölen, Stadt Quick edit Valid 2009-01-01 16074116
16075002 Birkenhügel Quick edit Valid 2009-01-01 16075002
16075003 Blankenberg Quick edit Valid 2009-01-01 16075003
16075004 Blankenstein Quick edit Valid 2009-01-01 16075004
16075006 Bodelwitz Quick edit Valid 2009-01-01 16075006
16075007 Breitenhain Quick edit Valid 2009-01-01 16075007
16075008 Bucha Quick edit Valid 2009-01-01 16075008
16075009 Burgk Quick edit Valid 2009-01-01 16075009
16075012 Chursdorf Quick edit Valid 2009-01-01 16075012
16075013 Crispendorf Quick edit Valid 2009-01-01 16075013
16075014 Dittersdorf Quick edit Valid 2009-01-01 16075014
16075016 Döbritz Quick edit Valid 2009-01-01 16075016
16075017 Dragensdorf Quick edit Valid 2009-01-01 16075017
16075018 Dreba Quick edit Valid 2009-01-01 16075018
16075019 Dreitzsch Quick edit Valid 2009-01-01 16075019
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?