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,621 to 10,640.First528529530531532533534535Last
Id Label Status Status Modified Notation
16067027 Goldbach Quick edit Valid 2009-01-01 16067027
16067029 Gotha, Stadt Quick edit Valid 2009-01-01 16067029
16067032 Gräfenhain Quick edit Valid 2009-01-01 16067032
16067033 Großfahner Quick edit Valid 2009-01-01 16067033
16067035 Haina Quick edit Valid 2009-01-01 16067035
16067036 Herrenhof Quick edit Valid 2009-01-01 16067036
16067037 Hochheim Quick edit Valid 2009-01-01 16067037
16067038 Hörselgau Quick edit Valid 2009-01-01 16067038
16067039 Hohenkirchen Quick edit Valid 2009-01-01 16067039
16067042 Laucha Quick edit Valid 2009-01-01 16067042
16067044 Luisenthal Quick edit Valid 2009-01-01 16067044
16067045 Mechterstädt Quick edit Valid 2009-01-01 16067045
16067046 Metebach Quick edit Valid 2009-01-01 16067046
16067047 Molschleben Quick edit Valid 2009-01-01 16067047
16067052 Nottleben Quick edit Valid 2009-01-01 16067052
16067053 Ohrdruf, Stadt Quick edit Valid 2009-01-01 16067053
16067054 Petriroda Quick edit Valid 2009-01-01 16067054
16067055 Pferdingsleben Quick edit Valid 2009-01-01 16067055
16067056 Remstädt Quick edit Valid 2009-01-01 16067056
16067059 Schwabhausen Quick edit Valid 2009-01-01 16067059
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?