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 141 to 160.First4567891011Last
Id Label Status Status Modified Notation
AT2211000 Hartberger-Gmoos Quick edit Valid 2018-01-19 AT2211000
AT2212000 Wörschacher Moos und ennsnahe Bereiche Quick edit Valid 2018-01-19 AT2212000
AT2213000 Steirische Grenzmur mit Gamlitzbach und Gnasbach Quick edit Valid 2018-01-19 AT2213000
AT2214000 Deutschlandsberger Klause Quick edit Valid 2018-01-19 AT2214000
AT2215000 Teile der Eisenerzer Alpen Quick edit Valid 2018-01-19 AT2215000
AT2216000 Kirchkogel bei Pernegg Quick edit Valid 2018-01-19 AT2216000
AT2217000 Peggauer Wand Quick edit Valid 2018-01-19 AT2217000
AT2218000 Feistritzklamm/Herberstein Quick edit Valid 2018-01-19 AT2218000
AT2219000 Teile des steirischen Nockgebietes Quick edit Valid 2018-01-19 AT2219000
AT2220000 Zirbitzkogel Quick edit Valid 2018-01-19 AT2220000
AT2221000 Gamperlacke Quick edit Valid 2018-01-19 AT2221000
AT2222000 Feistritz- und Krumbachgraben Quick edit Valid 2019-06-12 AT2222000
AT2223000 Pölshof bei Pöls Quick edit Valid 2018-01-19 AT2223000
AT2224000 Zlaimmöser-Moore / Weißenbachalm Quick edit Valid 2018-01-19 AT2224000
AT2225000 Demmerkogel-Südhänge, Wellinggraben mit Sulm-, Saggau- und Laßnitzabschnitten und Pößnitzbach Quick edit Valid 2018-01-19 AT2225000
AT2226000 Furtner Teich - Dürnberger-Moor Quick edit Valid 2018-01-19 AT2226000
AT2226001 Dürnberger Moor Quick edit Valid 2018-01-19 AT2226001
AT2226002 Furtner Teich Quick edit Valid 2018-01-19 AT2226002
AT2227000 Schluchtwald der Gulling Quick edit Valid 2018-01-19 AT2227000
AT2228000 Ramsauer Torf Quick edit Valid 2018-01-19 AT2228000
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?