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 2,501 to 2,520.First122123124125126127128129Last
Id Label Status Status Modified Notation
euProtectedAreaCode.CH20020 BADEPLATZ Quick edit Deprecated - retired 2025-01-29 CH20020
euProtectedAreaCode.CH20021 BADEPLATZ Quick edit Deprecated - retired 2025-01-29 CH20021
euProtectedAreaCode.CH20022 BADEPLATZ Quick edit Deprecated - retired 2025-01-29 CH20022
euProtectedAreaCode.CH20023 BADEPLATZ Quick edit Deprecated - retired 2025-01-29 CH20023
euProtectedAreaCode.CH20024 LAUI Quick edit Deprecated - retired 2025-01-29 CH20024
euProtectedAreaCode.CH20025 RODENBRUNEN Quick edit Valid - stable 2025-01-29 CH20025
euProtectedAreaCode.CH20026 PETRI Quick edit Deprecated - retired 2025-01-29 CH20026
euProtectedAreaCode.CH20027 ETZWILER Quick edit Deprecated - retired 2025-01-29 CH20027
euProtectedAreaCode.CH20028 RHEINKLINGEN Quick edit Deprecated - retired 2025-01-29 CH20028
euProtectedAreaCode.CH20029 ROSENWEIHER Quick edit Deprecated - retired 2025-01-29 CH20029
euProtectedAreaCode.CH2003 PLAGE SUCHARD Quick edit Deprecated - retired 2025-01-29 CH2003
euProtectedAreaCode.CH20030 LEUTSWIL Quick edit Deprecated - retired 2025-01-29 CH20030
euProtectedAreaCode.CH20031 RORERBRUCKE Quick edit Deprecated - retired 2025-01-29 CH20031
euProtectedAreaCode.CH20032 SCHWIMMBAD Quick edit Deprecated - retired 2025-01-29 CH20032
euProtectedAreaCode.CH20033 SCHWIMMBAD Quick edit Deprecated - retired 2025-01-29 CH20033
euProtectedAreaCode.CH20034 BADEPLATZ Quick edit Deprecated - retired 2025-01-29 CH20034
euProtectedAreaCode.CH20035 SEEBAD Quick edit Valid - stable 2025-01-29 CH20035
euProtectedAreaCode.CH20036 TRIBOLTINGEN Quick edit Deprecated - retired 2025-01-29 CH20036
euProtectedAreaCode.CH20037 MANNERBAD Quick edit Deprecated - retired 2025-01-29 CH20037
euProtectedAreaCode.CH20038 BADEPLATZ Quick edit Deprecated - retired 2025-01-29 CH20038
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?