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 101 to 120.First23456789Last
Id Label Status Status Modified Notation
euProtectedAreaCode.AL731 DHERMI Quick edit Valid - stable 2022-08-11 AL731
euProtectedAreaCode.AL732 PALASE Quick edit Valid - stable 2022-08-11 AL732
euProtectedAreaCode.AL733 PALASE Quick edit Valid - stable 2022-08-11 AL733
euProtectedAreaCode.AL734 LIVADHE Quick edit Valid - stable 2022-08-11 AL734
euProtectedAreaCode.AL735 LIVADHE Quick edit Valid - stable 2022-08-11 AL735
euProtectedAreaCode.AL736 JALE Quick edit Valid - stable 2022-08-11 AL736
euProtectedAreaCode.AL737 JALE Quick edit Valid - stable 2022-08-11 AL737
euProtectedAreaCode.AL738 LUKOVE Quick edit Valid - stable 2022-08-11 AL738
euProtectedAreaCode.AL739 LUKOVE Quick edit Valid - stable 2022-08-11 AL739
euProtectedAreaCode.AL740 LUKOVE Quick edit Valid - stable 2022-08-11 AL740
euProtectedAreaCode.AL801 SARANDE Quick edit Valid - stable 2022-08-11 AL801
euProtectedAreaCode.AL802 SARANDE Quick edit Valid - stable 2022-08-11 AL802
euProtectedAreaCode.AL803 SARANDE Quick edit Valid - stable 2022-08-11 AL803
euProtectedAreaCode.AL804 SARANDE Quick edit Valid - stable 2022-08-11 AL804
euProtectedAreaCode.AL805 SARANDE Quick edit Valid - stable 2022-08-11 AL805
euProtectedAreaCode.AL806 SARANDE Quick edit Valid - stable 2022-08-11 AL806
euProtectedAreaCode.AL807 KSAMIL Quick edit Valid - stable 2022-08-11 AL807
euProtectedAreaCode.AL808 KSAMIL Quick edit Valid - stable 2022-08-11 AL808
euProtectedAreaCode.AL809 KSAMIL Quick edit Valid - stable 2022-08-11 AL809
euProtectedAreaCode.AT1051051100150010 NATUBADESEE KONIGSDORF Quick edit Valid - stable 2022-08-11 AT1051051100150010
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?