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
dct:isReplacedBy Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
dct:replaces Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
hasIdentifierScheme Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Oct 2015
hasRelatedZone Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Feb 2016
hasSpecialisedZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
03 Nov 2015
hasZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
18 Oct 2016
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014
skos:exactMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

106,312 concepts found, displaying 481 to 500.First2122232425262728Last
Id Label Status Status Modified Notation
euProtectedAreaCode.ATPA153 SCHONGEBIET BLUNTAUTAL Quick edit Valid - stable 2022-08-11 ATPA153
euProtectedAreaCode.ATPA153W SCHONGEBIET BLUNTAUTAL Quick edit Deprecated - superseded 2022-08-11 ATPA153W
euProtectedAreaCode.ATPA155 KERNZONE LADINGER SPITZ/SAUALPE Quick edit Valid - stable 2022-08-11 ATPA155
euProtectedAreaCode.ATPA155W KERNZONE LADINGER SPITZ/SAUALPE Quick edit Deprecated - superseded 2022-08-11 ATPA155W
euProtectedAreaCode.ATPA156 KERNZONE PETZEN Quick edit Valid - stable 2022-08-11 ATPA156
euProtectedAreaCode.ATPA156W KERNZONE PETZEN Quick edit Deprecated - superseded 2022-08-11 ATPA156W
euProtectedAreaCode.ATPA157 KERNZONE STEINKOGEL/VÖLKERMARKT Quick edit Valid - stable 2022-08-11 ATPA157
euProtectedAreaCode.ATPA157W KERNZONE STEINKOGEL/VÖLKERMARKT Quick edit Deprecated - superseded 2022-08-11 ATPA157W
euProtectedAreaCode.ATPA158 KERNZONE KAPPEL/KRAPPFELD Quick edit Valid - stable 2022-08-11 ATPA158
euProtectedAreaCode.ATPA158W KERNZONE KAPPEL/KRAPPFELD Quick edit Deprecated - superseded 2022-08-11 ATPA158W
euProtectedAreaCode.ATPA159 KERNZONE KLAGENFURT OST Quick edit Valid - stable 2022-08-11 ATPA159
euProtectedAreaCode.ATPA159W KERNZONE KLAGENFURT OST Quick edit Deprecated - superseded 2022-08-11 ATPA159W
euProtectedAreaCode.ATPA15W SCHONGEBIET HEILQUELLEN OBERLAA Quick edit Deprecated - superseded 2022-08-11 ATPA15W
euProtectedAreaCode.ATPA16 SCHONGEBIET WR. NEUSTADT Quick edit Valid - stable 2022-08-11 ATPA16
euProtectedAreaCode.ATPA160 KERNZONE KRAINDORF/ST. VEIT Quick edit Valid - stable 2022-08-11 ATPA160
euProtectedAreaCode.ATPA160W KERNZONE KRAINDORF/ST. VEIT Quick edit Deprecated - superseded 2022-08-11 ATPA160W
euProtectedAreaCode.ATPA161 KERNZONE STRASCHITZ/KLAGENFURT Quick edit Valid - stable 2022-08-11 ATPA161
euProtectedAreaCode.ATPA161W KERNZONE STRASCHITZ/KLAGENFURT Quick edit Deprecated - superseded 2022-08-11 ATPA161W
euProtectedAreaCode.ATPA162 KERNZONE AUEN Quick edit Valid - stable 2022-08-11 ATPA162
euProtectedAreaCode.ATPA162W KERNZONE AUEN Quick edit Deprecated - superseded 2022-08-11 ATPA162W
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?