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
22 Nov 2024
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

138,256 concepts found, displaying 2,821 to 2,840.First138139140141142143144145Last
Id Label Status Status Modified Notation
euProtectedAreaCode.CH8002 CAMPING VORAUEN Quick edit Deprecated - retired 2025-01-29 CH8002
euProtectedAreaCode.CH8003 CAMPING GASI Quick edit Deprecated - retired 2025-01-29 CH8003
euProtectedAreaCode.CH90 ADIGE Quick edit Deprecated 2025-01-29 CH90
euProtectedAreaCode.CH9001 STRANDBAD SEELIKEN Quick edit Deprecated - superseded 2025-11-04 CH9001
euProtectedAreaCode.CH9002 STRANDBAD BRUEGGLI Quick edit Deprecated - superseded 2025-11-04 CH9002
euProtectedAreaCode.CH9003 CAMPING UNTERAEGERI Quick edit Deprecated - superseded 2025-11-04 CH9003
euProtectedAreaCode.CH9004 STRANDBAD LIDO Quick edit Deprecated - superseded 2025-11-04 CH9004
euProtectedAreaCode.CY0001457000000154 KARAFA Quick edit Valid - stable 2025-01-29 CY0001457000000154
euProtectedAreaCode.CY0001457000000155 KRYONERI Quick edit Valid - stable 2025-01-29 CY0001457000000155
euProtectedAreaCode.CY0001460000000151 OMEGA Quick edit Valid - stable 2025-01-29 CY0001460000000151
euProtectedAreaCode.CY0003100000000010 KONNOS Quick edit Valid - stable 2025-01-29 CY0003100000000010
euProtectedAreaCode.CY0003100000000011 LIMNARA Quick edit Valid - stable 2025-01-29 CY0003100000000011
euProtectedAreaCode.CY0003100000000012 GLYKI NERO Quick edit Valid - stable 2025-01-29 CY0003100000000012
euProtectedAreaCode.CY0003100000000013 PANTACHOU Quick edit Valid - stable 2025-01-29 CY0003100000000013
euProtectedAreaCode.CY0003100000000015 VATHIA GONIA Quick edit Valid - stable 2025-01-29 CY0003100000000015
euProtectedAreaCode.CY0003100000000016 NISSI Quick edit Valid - stable 2025-01-29 CY0003100000000016
euProtectedAreaCode.CY0003100000000017 LANDA Quick edit Valid - stable 2025-01-29 CY0003100000000017
euProtectedAreaCode.CY0003100000000018 MAKRONISOS Quick edit Valid - stable 2025-01-29 CY0003100000000018
euProtectedAreaCode.CY0003100000000019 AGIA THEKLA Quick edit Valid - stable 2025-01-29 CY0003100000000019
euProtectedAreaCode.CY0003100000000019A LOUMA MARINA AGIAS NAPAS Quick edit Valid - stable 2025-01-29 CY0003100000000019A
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?