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 201 to 220.First7891011121314Last
Id Label Status Status Modified Notation
7236 Gørlev Quick edit Valid 2013-05-30 7236
7237 Bakkendrup Quick edit Valid 2013-05-30 7237
7238 Kirke Helsinge Quick edit Valid 2013-05-30 7238
7239 Drøsselbjerg Quick edit Valid 2013-05-30 7239
7240 Tranebjerg Quick edit Valid 2013-05-30 7240
7241 Besser Quick edit Valid 2013-05-30 7241
7242 Onsbjerg Quick edit Valid 2013-05-30 7242
7243 Kolby Quick edit Valid 2013-05-30 7243
7244 Nordby Quick edit Valid 2013-05-30 7244
7245 Stenlille Quick edit Valid 2013-05-30 7245
7246 Orø Quick edit Valid 2013-05-30 7246
7247 Føllenslev Quick edit Valid 2013-05-30 7247
7248 Særslev Quick edit Valid 2013-05-30 7248
7249 Bregninge Quick edit Valid 2013-05-30 7249
7250 Bjergsted Quick edit Valid 2013-05-30 7250
7251 Viskinge Quick edit Valid 2013-05-30 7251
7252 Avnsø Quick edit Valid 2013-05-30 7252
7253 Værslev Quick edit Valid 2013-05-30 7253
7254 Jorløse Quick edit Valid 2013-05-30 7254
7255 Vallekilde Quick edit Valid 2013-05-30 7255
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?