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 161 to 180.First56789101112Last
Id Label Status Status Modified Notation
AT2229000 Teile des Steirischen Jogl- und Wechsellandes Quick edit Valid 2018-01-19 AT2229000
AT2229001 Oberlauf der Pinka Quick edit Valid 2018-01-19 AT2229001
AT2229002 Ennstal zwischen Liezen und Niederstuttern Quick edit Valid 2018-01-19 AT2229002
AT2230000 Teile des südoststeirischen Hügellandes inklusive Höll und Grabenlandbäche Quick edit Valid 2018-01-19 AT2230000
AT2231000 Weizklamm Quick edit Valid 2018-01-19 AT2231000
AT2232000 Buchenwälder bei Bruck an der Mur Quick edit Valid 2019-06-12 AT2232000
AT2233000 Raabklamm Quick edit Valid 2018-01-19 AT2233000
AT2234000 Breitenau - Lantsch Quick edit Valid 2018-01-19 AT2234000
AT2235000 Hochwechsel Quick edit Valid 2019-06-12 AT2235000
AT2236000 Ober- und Mittellauf der Mur mit Puxer Auwald, Puxer Wand und Gulsen Quick edit Valid 2018-01-19 AT2236000
AT2237000 Geländeteile im Umfeld des Dieslingsees Quick edit Valid 2019-06-12 AT2237000
AT2238000 Gersdorfer Altarm Quick edit Valid 2018-01-19 AT2238000
AT2239000 Teile der Hinteren Pölsenalm Quick edit Valid 2019-06-12 AT2239000
AT2240000 Ennsaltarme bei Niederstuttern Quick edit Valid 2018-01-19 AT2240000
AT2241000 Südlich gelegene Talbereiche der Göstlinger Alpen Quick edit Valid 2019-06-12 AT2241000
AT2242000 Schwarze und Weiße Sulm Quick edit Valid 2018-01-19 AT2242000
AT2243000 Totes Gebirge mit Altausseer See Quick edit Valid 2018-01-19 AT2243000
AT2244000 Flaumeichenwälder im Grazer Bergland Quick edit Valid 2018-01-19 AT2244000
AT2245000 Schloss Eggenberg Quick edit Valid 2018-01-19 AT2245000
AT2246000 Wildoner Buchkogel Quick edit Valid 2018-01-19 AT2246000
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?