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,241 to 1,260.First5960616263646566Last
Id Label Status Status Modified Notation
euProtectedAreaCode.BEVL_BGW_0061_M HEERBAAN Quick edit Valid - stable 2022-08-11 BEVL_BGW_0061_M
euProtectedAreaCode.BEVL_BGW_0062_M OPITTERKIEZEL Quick edit Valid - stable 2022-08-11 BEVL_BGW_0062_M
euProtectedAreaCode.BEVL_BGW_006_S BEERNEM Quick edit Valid - stable 2022-08-11 BEVL_BGW_006_S
euProtectedAreaCode.BEVL_BGW_0071_M VLAKENHOF PUT1 Quick edit Valid - stable 2022-08-11 BEVL_BGW_0071_M
euProtectedAreaCode.BEVL_BGW_0072_M VLAKENHOF PUT2 Quick edit Valid - stable 2022-08-11 BEVL_BGW_0072_M
euProtectedAreaCode.BEVL_BGW_0073_M VLAKENHOF PUT3 Quick edit Valid - stable 2022-08-11 BEVL_BGW_0073_M
euProtectedAreaCode.BEVL_BGW_0074_M VLAKENHOF PUT4 Quick edit Valid - stable 2022-08-11 BEVL_BGW_0074_M
euProtectedAreaCode.BEVL_BGW_0075_M VLAKENHOF PUT5 Quick edit Valid - stable 2022-08-11 BEVL_BGW_0075_M
euProtectedAreaCode.BEVL_BGW_0076_M VLAKENHOF PUT6 Quick edit Valid - stable 2022-08-11 BEVL_BGW_0076_M
euProtectedAreaCode.BEVL_BGW_0077_M VLAKENHOF PUT7 Quick edit Valid - stable 2022-08-11 BEVL_BGW_0077_M
euProtectedAreaCode.BEVL_BGW_007_S BEERSE Quick edit Valid - stable 2022-08-11 BEVL_BGW_007_S
euProtectedAreaCode.BEVL_BGW_008_M DIETS-HEUR Quick edit Valid - stable 2022-08-11 BEVL_BGW_008_M
euProtectedAreaCode.BEVL_BGW_008_S BIJLOKESTRAAT Quick edit Valid - stable 2022-08-11 BEVL_BGW_008_S
euProtectedAreaCode.BEVL_BGW_009_M LAUW-TONGEREN Quick edit Valid - stable 2022-08-11 BEVL_BGW_009_M
euProtectedAreaCode.BEVL_BGW_009_S BISSCHOPPEN Quick edit Valid - stable 2022-08-11 BEVL_BGW_009_S
euProtectedAreaCode.BEVL_BGW_010_S BOVELINGEN-RUKKELINGEN-LOON Quick edit Valid - stable 2022-08-11 BEVL_BGW_010_S
euProtectedAreaCode.BEVL_BGW_011_M MEERLE Quick edit Valid - stable 2022-08-11 BEVL_BGW_011_M
euProtectedAreaCode.BEVL_BGW_011_S BRASSCHAAT Quick edit Valid - stable 2022-08-11 BEVL_BGW_011_S
euProtectedAreaCode.BEVL_BGW_012_M BOLKSE HEIDE Quick edit Valid - stable 2022-08-11 BEVL_BGW_012_M
euProtectedAreaCode.BEVL_BGW_012_S DE WAMP Quick edit Valid - stable 2022-08-11 BEVL_BGW_012_S
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?