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:prefLabel Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

116 concepts found, displaying 101 to 116.First123456NextLast
Id Label Status Status Modified Notation
1203 Flaxweiler / Fluessweller Quick edit Valid 2013-05-31 1203
1204 Grevenmacher / Gréiwenmaacher Quick edit Valid 2013-05-31 1204
1205 Junglinster / Jonglënster Quick edit Valid 2013-05-31 1205
1206 Manternach Quick edit Valid 2013-05-31 1206
1207 Mertert / Mäertert Quick edit Valid 2013-05-31 1207
1209 Wormeldange / Wuermeldeng Quick edit Valid 2013-05-31 1209
1300 Bous / Bus Quick edit Valid 2013-05-31 1300
1301 Burmerange / Biermereng Quick edit Valid 2013-05-31 1301
1302 Dalheim / Duelem Quick edit Valid 2013-05-31 1302
1303 Lenningen / Lenneng Quick edit Valid 2013-05-31 1303
1304 Mondorf-les-Bains / Munneref Quick edit Valid 2013-05-31 1304
1305 Schengen Quick edit Valid 2013-05-31 1305
1306 Remich / Réimech Quick edit Valid 2013-05-31 1306
1307 Stadtbredimus / Stadbriedemes Quick edit Valid 2013-05-31 1307
1308 Waldbredimus / Waldbriedemes Quick edit Valid 2013-05-31 1308
1309 Wellenstein / Wellesteen Quick edit Valid 2013-05-31 1309
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?