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 6,001 to 6,020.First297298299300301302303304Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEPE_BW-60-9462 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-60-9462
euProtectedAreaCode.DEPE_BW-61-515 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-61-515
euProtectedAreaCode.DEPE_BW-8-3319 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-8-3319
euProtectedAreaCode.DEPE_BW-9-10940 NAME Quick edit Valid - stable 2025-01-29 DEPE_BW-9-10940
euProtectedAreaCode.DEPE_DESH_5000_01 STR Quick edit Valid - stable 2025-01-29 DEPE_DESH_5000_01
euProtectedAreaCode.DEPE_DESH_5000_02 BILLE Quick edit Valid - stable 2025-01-29 DEPE_DESH_5000_02
euProtectedAreaCode.DEPE_DESH_5000_1 W VII Quick edit Valid - stable 2025-01-29 DEPE_DESH_5000_1
euProtectedAreaCode.DEPE_DESH_9500_01 BONGSIELER KANAL Quick edit Valid - stable 2025-01-29 DEPE_DESH_9500_01
euProtectedAreaCode.DEPE_DESH_9500_02 TREENE Quick edit Valid - stable 2025-01-29 DEPE_DESH_9500_02
euProtectedAreaCode.DEPE_DESH_9500_1 W I Quick edit Valid - stable 2025-01-29 DEPE_DESH_9500_1
euProtectedAreaCode.DEPE_DESH_9500_2 W II Quick edit Valid - stable 2025-01-29 DEPE_DESH_9500_2
euProtectedAreaCode.DEPE_DESH_9500_3 W III Quick edit Valid - stable 2025-01-29 DEPE_DESH_9500_3
euProtectedAreaCode.DEPE_DESH_9500_4 W IV Quick edit Valid - stable 2025-01-29 DEPE_DESH_9500_4
euProtectedAreaCode.DEPE_DESH_9500_5 W V Quick edit Valid - stable 2025-01-29 DEPE_DESH_9500_5
euProtectedAreaCode.DEPE_DESH_9500_6 W VI Quick edit Valid - stable 2025-01-29 DEPE_DESH_9500_6
euProtectedAreaCode.DEPE_DESH_9500_7 W VII Quick edit Valid - stable 2025-01-29 DEPE_DESH_9500_7
euProtectedAreaCode.DEPE_DESH_9610_01 SCHWENTINE Quick edit Valid - stable 2025-01-29 DEPE_DESH_9610_01
euProtectedAreaCode.DEPE_DESH_9610_02 TRAVE Quick edit Valid - stable 2025-01-29 DEPE_DESH_9610_02
euProtectedAreaCode.DEPE_DESH_9610_1 O I Quick edit Valid - stable 2025-01-29 DEPE_DESH_9610_1
euProtectedAreaCode.DEPE_DESH_9610_2 O II Quick edit Valid - stable 2025-01-29 DEPE_DESH_9610_2
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?