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 96,741 to 96,760.First4,8344,8354,8364,8374,8384,8394,8404,841Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL3111906206000038 ASTUR Quick edit Valid - stable 2022-08-11 PL3111906206000038
euProtectedAreaCode.PL3111906206000045 KAPIELISKO NR 3 Quick edit Valid - stable 2022-08-11 PL3111906206000045
euProtectedAreaCode.PL3111907206000027 POMPKA Quick edit Valid - stable 2022-08-11 PL3111907206000027
euProtectedAreaCode.PL3120201106000021 KAPIELISKO NA ZALEWIE BOJARY Quick edit Valid - stable 2022-08-11 PL3120201106000021
euProtectedAreaCode.PL3120204206000033 KAPIELISKO ZALEW BISZCZA - ZARY Quick edit Valid - stable 2022-08-11 PL3120204206000033
euProtectedAreaCode.PL3120207406000041 ZALEW W JOZEFOWIE Quick edit Valid - stable 2022-08-11 PL3120207406000041
euProtectedAreaCode.PL3120303206000014 ZOLTANCE Quick edit Valid - stable 2022-08-11 PL3120303206000014
euProtectedAreaCode.PL3120303206000015 STAW Quick edit Valid - stable 2022-08-11 PL3120303206000015
euProtectedAreaCode.PL3120304206000017 HUSYNNE Quick edit Valid - stable 2022-08-11 PL3120304206000017
euProtectedAreaCode.PL3120306206000018 NATALIN Quick edit Valid - stable 2022-08-11 PL3120306206000018
euProtectedAreaCode.PL3120307206000016 MACZULY Quick edit Valid - stable 2022-08-11 PL3120307206000016
euProtectedAreaCode.PL3120311206000046 MAJDAN ZAHORODYNSKI Quick edit Valid - stable 2022-08-11 PL3120311206000046
euProtectedAreaCode.PL3120314206000019 DEBOWY LAS Quick edit Valid - stable 2022-08-11 PL3120314206000019
euProtectedAreaCode.PL3120608206000020 BIALY ROW Quick edit Deprecated - superseded 2022-08-11 PL3120608206000020
euProtectedAreaCode.PL3120608206000020A BIALY ROW Quick edit Valid - stable 2022-08-11 PL3120608206000020A
euProtectedAreaCode.PL3121808206000032 KAPIELISKO PRZY MOLO W MAJDANIE SOPOCKIM DRUGIM Quick edit Valid - stable 2022-08-11 PL3121808206000032
euProtectedAreaCode.PL3122004406000002 ZALEW W KRASNOBRODZIE Quick edit Valid - stable 2022-08-11 PL3122004406000002
euProtectedAreaCode.PL3122007206000012 MOCZYDLO Quick edit Valid - stable 2022-08-11 PL3122007206000012
euProtectedAreaCode.PL3122015406000011 STAWY ECHO Quick edit Valid - stable 2022-08-11 PL3122015406000011
euProtectedAreaCode.PL3126201106000013 GLINIANKI Quick edit Valid - stable 2022-08-11 PL3126201106000013
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?