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,741 to 1,760.First8485868788899091Last
Id Label Status Status Modified Notation
8785 Ådum Quick edit Valid 2013-05-30 8785
8786 Hoven Quick edit Valid 2013-05-30 8786
8787 Strellev Quick edit Valid 2013-05-30 8787
8788 Lyne Quick edit Valid 2013-05-30 8788
8789 Herning * Quick edit Valid 2013-05-30 8789
8790 Sankt Johannes * Quick edit Valid 2013-05-30 8790
8791 Fredens * Quick edit Valid 2013-05-30 8791
8792 Aulum Quick edit Valid 2013-05-30 8792
8793 Hodsager Quick edit Valid 2013-05-30 8793
8794 Vildbjerg Quick edit Valid 2013-05-30 8794
8795 Nøvling Quick edit Valid 2013-05-30 8795
8796 Timring Quick edit Valid 2013-05-30 8796
8797 Ørre Quick edit Valid 2013-05-30 8797
8798 Sinding Quick edit Valid 2013-05-30 8798
8799 Gjellerup Quick edit Valid 2013-05-30 8799
8800 Sunds Quick edit Valid 2013-05-30 8800
8801 Ilskov (delsogn) Quick edit Valid 2013-05-30 8801
8802 Ikast Quick edit Valid 2013-05-30 8802
8803 Rind Quick edit Valid 2013-05-30 8803
8804 Snejbjerg Quick edit Valid 2013-05-30 8804
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?