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,881 to 3,900.First191192193194195196197198Last
Id Label Status Status Modified Notation
euProtectedAreaCode.CZKO810202 VRBICKE JEZERO - PISKOVNA Quick edit Valid - stable 2025-01-29 CZKO810202
euProtectedAreaCode.CZKO810301 LOM - SVOBODNE HERMANICE Quick edit Valid - stable 2025-01-29 CZKO810301
euProtectedAreaCode.CZKO810303 VN SLEZSKA HARTA - LESKOVEC NAD MORAVICI Quick edit Valid - stable 2025-01-29 CZKO810303
euProtectedAreaCode.CZKO810304 VN SLEZSKA HARTA - NOVA PLAN Quick edit Valid - stable 2025-01-29 CZKO810304
euProtectedAreaCode.CZKO810306 VN SLEZSKA HARTA - ROUDNO I Quick edit Deprecated - retired 2025-11-04 CZKO810306
euProtectedAreaCode.CZKO810308 VN SLEZSKA HARTA - ROUDNO Quick edit Valid - stable 2025-11-04 CZKO810308
euProtectedAreaCode.CZKO810601 VN BASKA Quick edit Valid - stable 2025-01-29 CZKO810601
euProtectedAreaCode.CZKO810602 VN BRUSPERK I Quick edit Valid - stable 2025-01-29 CZKO810602
euProtectedAreaCode.CZKO810603 VN OLESNA - MISTEK Quick edit Valid - stable 2025-01-29 CZKO810603
euProtectedAreaCode.CZKO810604 VN OLESNA - PALKOVICE Quick edit Valid - stable 2025-01-29 CZKO810604
euProtectedAreaCode.CZKO810605 VN ZERMANICE - DOLNI DOMASLAVICE Quick edit Valid - stable 2025-01-29 CZKO810605
euProtectedAreaCode.CZKO810606 VN ZERMANICE - LUCINA Quick edit Valid - stable 2025-01-29 CZKO810606
euProtectedAreaCode.CZKO810607 VN ZERMANICE - SOBESOVICE Quick edit Valid - stable 2025-01-29 CZKO810607
euProtectedAreaCode.CZKO810801 VN TERLICKO - PACALUVKA Quick edit Valid - stable 2025-01-29 CZKO810801
euProtectedAreaCode.CZKO810802 VN TERLICKO - POD MOTELEM Quick edit Valid - stable 2025-01-29 CZKO810802
euProtectedAreaCode.CZKO810803 VN TERLICKO - TERLICKO STRED Quick edit Valid - stable 2025-01-29 CZKO810803
euProtectedAreaCode.CZKO811201 VN VETRKOVICE Quick edit Valid - stable 2025-01-29 CZKO811201
euProtectedAreaCode.CZKO811401 RYBNIK POD HRADEM Quick edit Valid - stable 2025-01-29 CZKO811401
euProtectedAreaCode.CZKO811501 VN CERTAK Quick edit Valid - stable 2025-01-29 CZKO811501
euProtectedAreaCode.CZKO811502 VN KACABAJA Quick edit Valid - stable 2025-01-29 CZKO811502
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?