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 841 to 860.First3940414243444546Last
Id Label Status Status Modified Notation
euProtectedAreaCode.BERW_AIEM18 PUITS DU MOULIN Quick edit Valid - stable 2025-01-29 BERW_AIEM18
euProtectedAreaCode.BERW_AMEL01_04 MODERSCHEID 17A Quick edit Valid - stable 2025-01-29 BERW_AMEL01_04
euProtectedAreaCode.BERW_AMEL02 HALENFELD CAPTAGE 14B Quick edit Valid - stable 2025-01-29 BERW_AMEL02
euProtectedAreaCode.BERW_AMEL03 SCHOPPEN CAPTAGE SE Quick edit Valid - stable 2025-01-29 BERW_AMEL03
euProtectedAreaCode.BERW_AMEL05 AMBLEVE WOLFSBUSCH I- RECHT WOLFSBUSCH II Quick edit Valid - stable 2025-01-29 BERW_AMEL05
euProtectedAreaCode.BERW_AMEL06 MODERSCHEID FORAGE CAPTAGE 19 Quick edit Valid - stable 2025-01-29 BERW_AMEL06
euProtectedAreaCode.BERW_AQUASAMBRE01 VIESVILLE 1- 2- 3- 4- THIMEON Quick edit Valid - stable 2025-01-29 BERW_AQUASAMBRE01
euProtectedAreaCode.BERW_AQUASAMBRE02 AISEAU FORGES-CASCADE P1- FORGES-TILLEUL P2- FAUBOURG P0- P01 Quick edit Valid - stable 2025-01-29 BERW_AQUASAMBRE02
euProtectedAreaCode.BERW_AQUASAMBRE03 CARNELLE P1- P2 Quick edit Valid - stable 2025-01-29 BERW_AQUASAMBRE03
euProtectedAreaCode.BERW_AQUASAMBRE04 DU BERGER-GALERIES-PUITS Quick edit Valid - stable 2025-01-29 BERW_AQUASAMBRE04
euProtectedAreaCode.BERW_ASBL-NOTREDAME-ORVAL FONTAINE MATHILDE- ABBAYE D ORVAL Quick edit Valid - stable 2025-01-29 BERW_ASBL-NOTREDAME-ORVAL
euProtectedAreaCode.BERW_CIDESER01 ROBECHIES - MON REVE- MON REVE P2 Quick edit Valid - stable 2025-01-29 BERW_CIDESER01
euProtectedAreaCode.BERW_CIESAC01 GRAND AVIN Quick edit Valid - stable 2025-01-29 BERW_CIESAC01
euProtectedAreaCode.BERW_CIESAC02 PETIT AVIN Quick edit Valid - stable 2025-01-29 BERW_CIESAC02
euProtectedAreaCode.BERW_CIESAC03 FOND SAINT MARTIN Quick edit Valid - stable 2025-01-29 BERW_CIESAC03
euProtectedAreaCode.BERW_CILE002 CAPTAGES DU NEBLON Quick edit Valid - stable 2025-01-29 BERW_CILE002
euProtectedAreaCode.BERW_CILE003 TRIFFOY-ROISEUX Quick edit Valid - stable 2025-01-29 BERW_CILE003
euProtectedAreaCode.BERW_CILE005 PECHET I- II Quick edit Valid - stable 2025-01-29 BERW_CILE005
euProtectedAreaCode.BERW_IDEN01 MARNAVE Quick edit Valid - stable 2025-01-29 BERW_IDEN01
euProtectedAreaCode.BERW_IDEN02 EN TIGE DE VILLE Quick edit Valid - stable 2025-01-29 BERW_IDEN02
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?