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 981 to 1,000.First4647484950515253Last
Id Label Status Status Modified Notation
01061031 Gribbohm Quick edit Valid 2009-01-01 01061031
01061033 Hadenfeld Quick edit Valid 2009-01-01 01061033
01061034 Heiligenstedten Quick edit Valid 2009-01-01 01061034
01061035 Heiligenstedtenerkamp Quick edit Valid 2009-01-01 01061035
01061036 Hennstedt Quick edit Valid 2009-01-01 01061036
01061037 Herzhorn Quick edit Valid 2009-01-01 01061037
01061038 Hingstheide Quick edit Valid 2009-01-01 01061038
01061039 Hodorf Quick edit Valid 2009-01-01 01061039
01061040 Hohenaspe Quick edit Valid 2009-01-01 01061040
01061041 Hohenfelde Quick edit Valid 2009-01-01 01061041
01061042 Hohenlockstedt Quick edit Valid 2009-01-01 01061042
01061043 Holstenniendorf Quick edit Valid 2009-01-01 01061043
01061044 Horst (Holstein) Quick edit Valid 2009-01-01 01061044
01061045 Huje Quick edit Valid 2009-01-01 01061045
01061046 Itzehoe, Stadt Quick edit Valid 2009-01-01 01061046
01061047 Kaaks Quick edit Valid 2009-01-01 01061047
01061048 Kaisborstel Quick edit Valid 2009-01-01 01061048
01061049 Kellinghusen, Stadt Quick edit Valid 2009-01-01 01061049
01061050 Kiebitzreihe Quick edit Valid 2009-01-01 01061050
01061052 Kleve Quick edit Valid 2009-01-01 01061052
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?