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
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014
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 (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

28,131 concepts found, displaying 281 to 300.First1112131415161718Last
Id Label Status Status Modified Notation
AT3238000 Pongauer Taurachtal Quick edit Valid 2018-01-19 AT3238000
AT3239000 Königsbachtal Quick edit Valid 2018-01-19 AT3239000
AT3240000 Drossen Quick edit Valid 2018-01-19 AT3240000
AT3241000 Streuwiese am Salzweg Quick edit Valid 2018-01-19 AT3241000
AT3242000 Lonka-Mäander Quick edit Valid 2018-01-19 AT3242000
AT3243000 Althofener Moos Quick edit Valid 2018-01-19 AT3243000
AT3244000 Steindorf - Am Moos Quick edit Valid 2018-01-19 AT3244000
AT3245000 Lucia-Lacke Quick edit Valid 2018-01-19 AT3245000
AT3246000 Vordergnadenalm Quick edit Valid 2019-06-12 AT3246000
AT3247000 Fraham-Aag-Zellhof Quick edit Valid 2019-06-12 AT3247000
AT3248000 Prähauserbauerwiese Quick edit Valid 2019-06-12 AT3248000
AT3249000 Unterfelben Quick edit Valid 2019-06-12 AT3249000
AT3250000 Gschwendter Moos Quick edit Valid 2019-06-12 AT3250000
AT3251000 Nikolausberg Quick edit Valid 2019-06-12 AT3251000
AT3252000 Hintergnadenalm Quick edit Valid 2019-06-12 AT3252000
AT3253000 Unkenberger Mähder Quick edit Valid 2019-06-12 AT3253000
AT3301000 Hohe Tauern, Tirol Quick edit Valid 2018-01-19 AT3301000
AT3302000 Vilsalpsee Quick edit Valid 2018-01-19 AT3302000
AT3303000 Valsertal Quick edit Valid 2018-01-19 AT3303000
AT3304000 Karwendel Quick edit Valid 2018-01-19 AT3304000
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?