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
skos:narrowMatch 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

99 concepts found, displaying 1 to 20.FirstPrev12345Last
Id Label Status Status Modified Notation
101 København Quick edit Valid 2013-06-05 101
147 Frederiksberg Quick edit Valid 2013-06-05 147
151 Ballerup Quick edit Valid 2013-06-05 151
153 Brøndby Quick edit Valid 2013-06-05 153
155 Dragør Quick edit Valid 2013-06-05 155
157 Gentofte Quick edit Valid 2013-06-05 157
159 Gladsaxe Quick edit Valid 2013-06-05 159
161 Glostrup Quick edit Valid 2013-06-05 161
163 Herlev Quick edit Valid 2013-06-05 163
165 Albertslund Quick edit Valid 2013-06-05 165
167 Hvidovre Quick edit Valid 2013-06-05 167
169 Høje-Taastrup Quick edit Valid 2013-06-05 169
173 Lyngby-Taarbæk Quick edit Valid 2013-06-05 173
175 Rødovre Quick edit Valid 2013-06-05 175
183 Ishøj Quick edit Valid 2013-06-05 183
185 Tårnby Quick edit Valid 2013-06-05 185
187 Vallensbæk Quick edit Valid 2013-06-05 187
190 Furesø Quick edit Valid 2013-06-05 190
201 Allerød Quick edit Valid 2013-06-05 201
210 Fredensborg Quick edit Valid 2013-06-05 210
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?