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

2,122 concepts found, displaying 1,161 to 1,180.First5556575859606162Last
Id Label Status Status Modified Notation
8201 Vindblæs Quick edit Valid 2013-05-30 8201
8202 Hem Quick edit Valid 2013-05-30 8202
8203 Sem Quick edit Valid 2013-05-30 8203
8204 Sønder Onsild Quick edit Valid 2013-05-30 8204
8205 Nørre Onsild Quick edit Valid 2013-05-30 8205
8206 Hvornum Quick edit Valid 2013-05-30 8206
8207 Snæbum Quick edit Valid 2013-05-30 8207
8208 Borup Quick edit Valid 2013-05-30 8208
8209 Gimming Quick edit Valid 2013-05-30 8209
8210 Lem Quick edit Valid 2013-05-30 8210
8211 Harridslev Quick edit Valid 2013-05-30 8211
8212 Albæk Quick edit Valid 2013-05-30 8212
8213 Kristrup Quick edit Valid 2013-05-30 8213
8214 Virring Quick edit Valid 2013-05-30 8214
8215 Essenbæk Quick edit Valid 2013-05-30 8215
8216 Hørning Quick edit Valid 2013-05-30 8216
8217 Fausing (delsogn) Quick edit Valid 2013-05-30 8217
8218 Auning Quick edit Valid 2013-05-30 8218
8219 Marie Magdalene Quick edit Valid 2013-05-30 8219
8220 Koed Quick edit Valid 2013-05-30 8220
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?