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 3,861 to 3,880.First190191192193194195196197Last
Id Label Status Status Modified Notation
euProtectedAreaCode.CZKO620305 VN BRNENSKA PREHRADA - OSADA Quick edit Valid - stable 2025-01-29 CZKO620305
euProtectedAreaCode.CZKO621802 VN LUCINA Quick edit Valid - stable 2025-01-29 CZKO621802
euProtectedAreaCode.CZKO622002 VRANOVSKA PREHRADA - PLAZ BITOV Quick edit Deprecated - retired 2025-01-29 CZKO622002
euProtectedAreaCode.CZKO622003 VRANOVSKA PREHRADA - PLAZ VRANOV Quick edit Valid - stable 2025-01-29 CZKO622003
euProtectedAreaCode.CZKO622004 VN VYROVICE Quick edit Deprecated - retired 2025-01-29 CZKO622004
euProtectedAreaCode.CZKO622005 VRANOVSKA PREHRADA - BITOV KOPANINKY Quick edit Deprecated - retired 2025-01-29 CZKO622005
euProtectedAreaCode.CZKO710701 PODEBRADY - U PRISTAVISTE Quick edit Valid - stable 2025-01-29 CZKO710701
euProtectedAreaCode.CZKO710702 PODEBRADY - PLANE LOUCKY Quick edit Valid - stable 2025-01-29 CZKO710702
euProtectedAreaCode.CZKO710801 VN PLUMLOV Quick edit Valid - stable 2025-01-29 CZKO710801
euProtectedAreaCode.CZKO720401 VN LUHACOVICE - U HRAZE Quick edit Valid - stable 2025-01-29 CZKO720401
euProtectedAreaCode.CZKO720402 VN LUHACOVICE - KEMP Quick edit Valid - stable 2025-01-29 CZKO720402
euProtectedAreaCode.CZKO720501 PAHRBEK NAPAJEDLA Quick edit Valid - stable 2025-01-29 CZKO720501
euProtectedAreaCode.CZKO720502 STERKAC OTROKOVICE Quick edit Valid - stable 2025-01-29 CZKO720502
euProtectedAreaCode.CZKO720601 VN HORNI BECVA Quick edit Valid - stable 2025-01-29 CZKO720601
euProtectedAreaCode.CZKO721101 VN VSEMINA Quick edit Valid - stable 2025-01-29 CZKO721101
euProtectedAreaCode.CZKO721201 VN BYSTRICKA - U HRAZE Quick edit Valid - stable 2025-01-29 CZKO721201
euProtectedAreaCode.CZKO721202 VN BYSTRICKA - U PLAZE Quick edit Valid - stable 2025-01-29 CZKO721202
euProtectedAreaCode.CZKO721203 NOVY HROZENKOV Quick edit Valid - stable 2025-01-29 CZKO721203
euProtectedAreaCode.CZKO810101 BILOVECKY RYBNIK - UDOLI MLADYCH Quick edit Valid - stable 2025-01-29 CZKO810101
euProtectedAreaCode.CZKO810201 KALISOVO JEZERO - PISKOVNA Quick edit Valid - stable 2025-01-29 CZKO810201
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?