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 261 to 280.First1011121314151617Last
Id Label Status Status Modified Notation
AT3218000 Hochgimpling Quick edit Valid 2018-01-19 AT3218000
AT3219000 Gernfilzen-Bannwald Quick edit Valid 2018-01-19 AT3219000
AT3220000 Kematen Quick edit Valid 2018-01-19 AT3220000
AT3221000 Joching Quick edit Valid 2018-01-19 AT3221000
AT3222000 Moore am Überling Quick edit Valid 2018-01-19 AT3222000
AT3223000 Salzachauen, Salzburg Quick edit Valid 2018-01-19 AT3223000
AT3224000 Entrische Kirche Quick edit Valid 2018-01-19 AT3224000
AT3225000 Weidmoos Quick edit Valid 2018-01-19 AT3225000
AT3226000 Zinkenbach-Karlgraben Quick edit Valid 2018-01-19 AT3226000
AT3227000 Untersberg-Vorland Quick edit Valid 2018-01-19 AT3227000
AT3228000 Bürmooser Moor Quick edit Valid 2018-01-19 AT3228000
AT3229000 Nordmoor am Mattsee Quick edit Valid 2018-01-19 AT3229000
AT3230000 Zeller See Südufer Quick edit Valid 2018-01-19 AT3230000
AT3231000 Mooshamer Moos Ost Quick edit Valid 2018-01-19 AT3231000
AT3232000 Kopfweiden am Almkanal Quick edit Valid 2018-01-19 AT3232000
AT3233000 Pfarrkirche St. Georgen bei Salzburg Quick edit Valid 2018-01-19 AT3233000
AT3234000 Kendlbruckergraben - Hinteralm Quick edit Valid 2018-01-19 AT3234000
AT3235000 Hinterrieding-Wasserfallkar Quick edit Valid 2018-01-19 AT3235000
AT3236000 Rupanin Quick edit Valid 2018-01-19 AT3236000
AT3237000 Georgenberg Quick edit Valid 2018-01-19 AT3237000
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?