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 741 to 760.First3435363738394041Last
Id Label Status Status Modified Notation
euProtectedAreaCode.ATPA91 FEHRING Quick edit Valid - stable 2022-08-11 ATPA91
euProtectedAreaCode.ATPA91W FEHRING Quick edit Deprecated - superseded 2022-08-11 ATPA91W
euProtectedAreaCode.ATPA92 DEUTSCH GORITZ Quick edit Valid - stable 2022-08-11 ATPA92
euProtectedAreaCode.ATPA94 BAD GLEICHENBERG Quick edit Valid - stable 2022-08-11 ATPA94
euProtectedAreaCode.ATPA95 JOHANNESBRUNNEN Quick edit Valid - stable 2022-08-11 ATPA95
euProtectedAreaCode.ATPA96 GRAZ-ANDRITZ Quick edit Valid - stable 2022-08-11 ATPA96
euProtectedAreaCode.ATPA97 FELDBACH Quick edit Valid - stable 2022-08-11 ATPA97
euProtectedAreaCode.ATPA97W FELDBACH Quick edit Deprecated - superseded 2022-08-11 ATPA97W
euProtectedAreaCode.ATPA98 LEOBEN-WINKL Quick edit Valid - stable 2022-08-11 ATPA98
euProtectedAreaCode.ATPA98W LEOBEN-WINKL Quick edit Deprecated - superseded 2022-08-11 ATPA98W
euProtectedAreaCode.ATPA99 RAX - SCHNEEBERG - SCHNEEALPE Quick edit Valid - stable 2022-08-11 ATPA99
euProtectedAreaCode.ATPA9W SCHONGEBIET WIESELBURG Quick edit Deprecated - superseded 2022-08-11 ATPA9W
euProtectedAreaCode.ATRA_1_CM AUSTRIA Quick edit Valid - stable 2022-08-11 ATRA_1_CM
euProtectedAreaCode.BE1 BRUSSEL REGION Quick edit Valid - stable 2022-08-11 BE1
euProtectedAreaCode.BE2400022000000B04 RENIPONT BEACH Quick edit Valid - stable 2022-08-11 BE2400022000000B04
euProtectedAreaCode.BE3 FLEMISH REGION Quick edit Valid - stable 2022-08-11 BE3
euProtectedAreaCode.BE3200001000000E02 CLAIRE-FONTAINE LAKE Quick edit Valid - stable 2022-08-11 BE3200001000000E02
euProtectedAreaCode.BE3200012000000E05 LA MARLETTE IN SENEFFE Quick edit Valid - stable 2022-08-11 BE3200012000000E05
euProtectedAreaCode.BE3300007000000E03 THE GRAND LARGE IN NIMY Quick edit Valid - stable 2022-08-11 BE3300007000000E03
euProtectedAreaCode.BE3600006000000E01 FERONVAL LAKE Quick edit Valid - stable 2022-08-11 BE3600006000000E01
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?