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 3,741 to 3,760.First184185186187188189190191Last
Id Label Status Status Modified Notation
euProtectedAreaCode.CZKO212302 VN ORLIK - POPELIKY Quick edit Valid - stable 2022-08-11 CZKO212302
euProtectedAreaCode.CZKO212303 VN ORLIK - TRHOVKY Quick edit Valid - stable 2022-08-11 CZKO212303
euProtectedAreaCode.CZKO310301 VN LIPNO - PLAZ CERNA V POSUMAVI Quick edit Valid - stable 2022-08-11 CZKO310301
euProtectedAreaCode.CZKO310302 VN LIPNO - PLAZ HORNI PLANA Quick edit Valid - stable 2022-08-11 CZKO310302
euProtectedAreaCode.CZKO310303 VN LIPNO - PLAZ LIPNO NAD VLTAVOU Quick edit Valid - stable 2022-08-11 CZKO310303
euProtectedAreaCode.CZKO310701 VN ORLIK - ATC RADAVA Quick edit Valid - stable 2022-08-11 CZKO310701
euProtectedAreaCode.CZKO310801 VN ORLIK - VEREJNE TABORISTE PODOLSKO Quick edit Valid - stable 2022-08-11 CZKO310801
euProtectedAreaCode.CZKO310802 VN ORLIK - VEREJNE TABORISTE VOJNIKOV Quick edit Deprecated - retired 2022-08-11 CZKO310802
euProtectedAreaCode.CZKO311401 RYBNIK HEJTMAN Quick edit Valid - stable 2022-08-11 CZKO311401
euProtectedAreaCode.CZKO311402 STANKOVSKY RYBNIK Quick edit Valid - stable 2022-08-11 CZKO311402
euProtectedAreaCode.CZKO320501 RYBNIK HNACOV Quick edit Valid - stable 2022-08-11 CZKO320501
euProtectedAreaCode.CZKO320502 RYBNIK VALCHA Quick edit Deprecated - retired 2022-08-11 CZKO320502
euProtectedAreaCode.CZKO320801 VN HRACHOLUSKY - NA RADOSTI Quick edit Valid - stable 2022-08-11 CZKO320801
euProtectedAreaCode.CZKO320802 VN HRACHOLUSKY - HRAZ Quick edit Valid - stable 2022-08-11 CZKO320802
euProtectedAreaCode.CZKO320901 LOM - JEZIRKO KOSUTKA Quick edit Valid - stable 2022-08-11 CZKO320901
euProtectedAreaCode.CZKO320902 KAMENNY RYBNIK Quick edit Valid - stable 2022-08-11 CZKO320902
euProtectedAreaCode.CZKO320903 SENECKY RYBNIK Quick edit Valid - stable 2022-08-11 CZKO320903
euProtectedAreaCode.CZKO320904 SIDLOVSKY RYBNIK Quick edit Valid - stable 2022-08-11 CZKO320904
euProtectedAreaCode.CZKO320905 VELKY BOLEVECKY RYBNIK - HRAZ Quick edit Valid - stable 2022-08-11 CZKO320905
euProtectedAreaCode.CZKO320906 VELKY BOLEVECKY RYBNIK - OSTENDE Quick edit Valid - stable 2022-08-11 CZKO320906
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?