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 21 to 40.First12345Last
Id Label Status Status Modified Notation
217 Helsingør Quick edit Valid 2013-06-05 217
219 Hillerød Quick edit Valid 2013-06-05 219
223 Hørsholm Quick edit Valid 2013-06-05 223
230 Rudersdal Quick edit Valid 2013-06-05 230
240 Egedal Quick edit Valid 2013-06-05 240
250 Frederikssund Quick edit Valid 2013-06-05 250
253 Greve Quick edit Valid 2013-06-05 253
259 Køge Quick edit Valid 2013-06-05 259
260 Frederiksværk-Hundested Quick edit Valid 2013-06-05 260
265 Roskilde Quick edit Valid 2013-06-05 265
269 Solrød Quick edit Valid 2013-06-05 269
270 Gribskov Quick edit Valid 2013-06-05 270
306 Odsherred Quick edit Valid 2013-06-05 306
316 Holbæk Quick edit Valid 2013-06-05 316
326 Kalundborg Quick edit Valid 2013-06-05 326
329 Ringsted Quick edit Valid 2013-06-05 329
330 Slagelse Quick edit Valid 2013-06-05 330
336 Stevns Quick edit Valid 2013-06-05 336
340 Sorø Quick edit Valid 2013-06-05 340
350 Lejre Quick edit Valid 2013-06-05 350
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?