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
29 Oct 2015
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

106,312 concepts found, displaying 1,141 to 1,160.First5455565758596061Last
Id Label Status Status Modified Notation
euProtectedAreaCode.BERW_SWDE014 HEUVEL P1, G1 Quick edit Valid - stable 2022-08-11 BERW_SWDE014
euProtectedAreaCode.BERW_SWDE015 EBEN-EMAEL P1 Quick edit Valid - stable 2022-08-11 BERW_SWDE015
euProtectedAreaCode.BERW_SWDE016 BAS-SLINS P1 Quick edit Valid - stable 2022-08-11 BERW_SWDE016
euProtectedAreaCode.BERW_SWDE017 TAMIZON E1 Quick edit Valid - stable 2022-08-11 BERW_SWDE017
euProtectedAreaCode.BERW_SWDE018 BLATON P1, P2, P3, CARRIERE C1,C2 Quick edit Valid - stable 2022-08-11 BERW_SWDE018
euProtectedAreaCode.BERW_SWDE020 OBROECHEUIL P1, CASTEAU P2, THIEUSIES OBROECHEUIL P3 Quick edit Valid - stable 2022-08-11 BERW_SWDE020
euProtectedAreaCode.BERW_SWDE021 CHIEVRES P1 Quick edit Valid - stable 2022-08-11 BERW_SWDE021
euProtectedAreaCode.BERW_SWDE023 PRIEURE P1, P2 Quick edit Valid - stable 2022-08-11 BERW_SWDE023
euProtectedAreaCode.BERW_SWDE024 GROGNEAU DINANT D1, THYNES-LISOGNE D1, CRAHIATS E1 Quick edit Valid - stable 2022-08-11 BERW_SWDE024
euProtectedAreaCode.BERW_SWDE025 ESTINNES-AU-VAL P1 Quick edit Valid - stable 2022-08-11 BERW_SWDE025
euProtectedAreaCode.BERW_SWDE026 VILLERS-PERWIN B2, VILLERS-PERWIN B3, VILLERS B4,VILLERS B5, VILLERS B6, VILLERS C1, VILLERS C2 Quick edit Valid - stable 2022-08-11 BERW_SWDE026
euProtectedAreaCode.BERW_SWDE028 MORIALME P1, P2 Quick edit Valid - stable 2022-08-11 BERW_SWDE028
euProtectedAreaCode.BERW_SWDE029 WANSON G1, CHASSEPIERRE VILLAGE S1, S2, S2BIS, S3, S4, S5, WANSON G1 Quick edit Valid - stable 2022-08-11 BERW_SWDE029
euProtectedAreaCode.BERW_SWDE031 MOUSTIER P1, HACQUEGNIES P2 Quick edit Valid - stable 2022-08-11 BERW_SWDE031
euProtectedAreaCode.BERW_SWDE032 BOSSIERE G1 Quick edit Valid - stable 2022-08-11 BERW_SWDE032
euProtectedAreaCode.BERW_SWDE033 GRAND RENG SOURCE DE LA TROUILLE P1, P2, P3, P4 Quick edit Valid - stable 2022-08-11 BERW_SWDE033
euProtectedAreaCode.BERW_SWDE035 AVIN P1, P2 Quick edit Valid - stable 2022-08-11 BERW_SWDE035
euProtectedAreaCode.BERW_SWDE036 PRE DES AVOCATS, HASTERE P2 Quick edit Valid - stable 2022-08-11 BERW_SWDE036
euProtectedAreaCode.BERW_SWDE037 ST-VAAST P1, PUITS JORIS P2 Quick edit Valid - stable 2022-08-11 BERW_SWDE037
euProtectedAreaCode.BERW_SWDE039 SPIENNES G1, P1 Quick edit Valid - stable 2022-08-11 BERW_SWDE039
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?