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 5,941 to 5,960.First294295296297298299300301Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEPE_BW-19-6955 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-19-6955
euProtectedAreaCode.DEPE_BW-19-6959 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-19-6959
euProtectedAreaCode.DEPE_BW-2-515 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-2-515
euProtectedAreaCode.DEPE_BW-2-530 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-2-530
euProtectedAreaCode.DEPE_BW-2-565 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-2-565
euProtectedAreaCode.DEPE_BW-2-9527 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-2-9527
euProtectedAreaCode.DEPE_BW-2-9556 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-2-9556
euProtectedAreaCode.DEPE_BW-20-6738 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-20-6738
euProtectedAreaCode.DEPE_BW-20-6767 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-20-6767
euProtectedAreaCode.DEPE_BW-21-6921 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-21-6921
euProtectedAreaCode.DEPE_BW-22-12505 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-22-12505
euProtectedAreaCode.DEPE_BW-23-12461 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-23-12461
euProtectedAreaCode.DEPE_BW-23-6836 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-23-6836
euProtectedAreaCode.DEPE_BW-23-6886 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-23-6886
euProtectedAreaCode.DEPE_BW-24-6736 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-24-6736
euProtectedAreaCode.DEPE_BW-26-6611 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-26-6611
euProtectedAreaCode.DEPE_BW-27-5755 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-27-5755
euProtectedAreaCode.DEPE_BW-27-5772 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-27-5772
euProtectedAreaCode.DEPE_BW-27-5809 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-27-5809
euProtectedAreaCode.DEPE_BW-27-5836 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-27-5836
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?