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,581 to 3,600.First176177178179180181182183Last
Id Label Status Status Modified Notation
euProtectedAreaCode.CZ310 PISECNY RYBNIK Quick edit Valid - stable 2025-01-29 CZ310
euProtectedAreaCode.CZ313 PLACKY Quick edit Valid - stable 2025-01-29 CZ313
euProtectedAreaCode.CZ315 PLANE LOUCKY Quick edit Valid - stable 2025-01-29 CZ315
euProtectedAreaCode.CZ321 POD JURASKOU Quick edit Valid - stable 2025-01-29 CZ321
euProtectedAreaCode.CZ324 POD SIPINEM Quick edit Valid - stable 2025-01-29 CZ324
euProtectedAreaCode.CZ328 PODHRAZSKY RYBNIK Quick edit Valid - stable 2025-01-29 CZ328
euProtectedAreaCode.CZ329 POLABSKA CERNAVA Quick edit Valid - stable 2025-01-29 CZ329
euProtectedAreaCode.CZ330 POLANSKY LES Quick edit Valid - stable 2025-01-29 CZ330
euProtectedAreaCode.CZ362 RANSPURK Quick edit Valid - stable 2025-01-29 CZ362
euProtectedAreaCode.CZ363 RASELINISTE HAAR Quick edit Valid - stable 2025-01-29 CZ363
euProtectedAreaCode.CZ365 RASELINISTE JIZERKY Quick edit Valid - stable 2025-01-29 CZ365
euProtectedAreaCode.CZ366 RASELINISTE JIZERY Quick edit Valid - stable 2025-01-29 CZ366
euProtectedAreaCode.CZ367 RASELINISTE SKRITEK Quick edit Valid - stable 2025-01-29 CZ367
euProtectedAreaCode.CZ370 RECKOV Quick edit Valid - stable 2025-01-29 CZ370
euProtectedAreaCode.CZ371 REJVIZ Quick edit Valid - stable 2025-01-29 CZ371
euProtectedAreaCode.CZ375 RUDA Quick edit Valid - stable 2025-01-29 CZ375
euProtectedAreaCode.CZ378 RYBI LOUCKY Quick edit Valid - stable 2025-01-29 CZ378
euProtectedAreaCode.CZ379 RYCHORY Quick edit Deprecated 2025-01-29 CZ379
euProtectedAreaCode.CZ381 REZABINEC A REZABINECKE TUNE Quick edit Valid - stable 2025-01-29 CZ381
euProtectedAreaCode.CZ386 SITOVKA Quick edit Valid - stable 2025-01-29 CZ386
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?