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,041 to 6,060.First299300301302303304305306Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEPE_NWF021 FERNDORFBACH Quick edit Valid - stable 2025-01-29 DEPE_NWF021
euProtectedAreaCode.DEPE_NWF022 GROE AUE Quick edit Valid - stable 2025-01-29 DEPE_NWF022
euProtectedAreaCode.DEPE_NWF023 GROE AUE Quick edit Valid - stable 2025-01-29 DEPE_NWF023
euProtectedAreaCode.DEPE_NWF024 HENNETALSPERRE Quick edit Valid - stable 2025-01-29 DEPE_NWF024
euProtectedAreaCode.DEPE_NWF025 HESSEL Quick edit Valid - stable 2025-01-29 DEPE_NWF025
euProtectedAreaCode.DEPE_NWF026 HESSEL Quick edit Valid - stable 2025-01-29 DEPE_NWF026
euProtectedAreaCode.DEPE_NWF027 HNNE Quick edit Valid - stable 2025-01-29 DEPE_NWF027
euProtectedAreaCode.DEPE_NWF028 INDE Quick edit Valid - stable 2025-01-29 DEPE_NWF028
euProtectedAreaCode.DEPE_NWF029 ISSEL Quick edit Valid - stable 2025-01-29 DEPE_NWF029
euProtectedAreaCode.DEPE_NWF030 LAHN Quick edit Valid - stable 2025-01-29 DEPE_NWF030
euProtectedAreaCode.DEPE_NWF031 LENNE Quick edit Valid - stable 2025-01-29 DEPE_NWF031
euProtectedAreaCode.DEPE_NWF032 LIPPE Quick edit Valid - stable 2025-01-29 DEPE_NWF032
euProtectedAreaCode.DEPE_NWF033 LIPPE Quick edit Valid - stable 2025-01-29 DEPE_NWF033
euProtectedAreaCode.DEPE_NWF034 LISTERTALSPERRE Quick edit Valid - stable 2025-01-29 DEPE_NWF034
euProtectedAreaCode.DEPE_NWF035 MHNETALSPERRE Quick edit Valid - stable 2025-01-29 DEPE_NWF035
euProtectedAreaCode.DEPE_NWF036 MNSTERSCHE AA Quick edit Valid - stable 2025-01-29 DEPE_NWF036
euProtectedAreaCode.DEPE_NWF037 NETHE Quick edit Valid - stable 2025-01-29 DEPE_NWF037
euProtectedAreaCode.DEPE_NWF038 NIERS Quick edit Valid - stable 2025-01-29 DEPE_NWF038
euProtectedAreaCode.DEPE_NWF039 RHEIN Quick edit Valid - stable 2025-01-29 DEPE_NWF039
euProtectedAreaCode.DEPE_NWF040 RUHR Quick edit Valid - stable 2025-01-29 DEPE_NWF040
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?