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,021 to 96,040.First4,7984,7994,8004,8014,8024,8034,8044,805Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL1260804514000006 ZEGRZE WARSZAWSKA Quick edit Deprecated - retired 2022-08-11 PL1260804514000006
euProtectedAreaCode.PL1261401114000056 KAPIELISKO PRZY TARGOWISKU MIEJSKIM W NOWYM DWORZE MAZOWIECKIM Quick edit Valid - stable 2022-08-11 PL1261401114000056
euProtectedAreaCode.PL1261401114000057 KAPIELISKO PRZY NOWODWORSKIM WODNYM OCHOTNICZYM POGOTOWIU RATUNKOWYM Quick edit Valid - stable 2022-08-11 PL1261401114000057
euProtectedAreaCode.PL1261708214000034 KAPIELISKO W KACKU Quick edit Valid - stable 2022-08-11 PL1261708214000034
euProtectedAreaCode.PL1262102114000042 KAPIELISKO ZORGANIZOWANE NA WYDZIELONYM FRAGMENCIE ZBIORNIKA WODNEGO GLINIANKA HOSERA Quick edit Valid - stable 2022-08-11 PL1262102114000042
euProtectedAreaCode.PL1263404114000046 GLINIANKI ZIELONKA Quick edit Valid - stable 2022-08-11 PL1263404114000046
euProtectedAreaCode.PL1263801114000035 ZALEW ZYRARDOWSKI Quick edit Valid - stable 2022-08-11 PL1263801114000035
euProtectedAreaCode.PL1276501114000055 JEZIORKO CZERNIAKOWSKIE Quick edit Valid - stable 2022-08-11 PL1276501114000055
euProtectedAreaCode.PL14197 WIGIERSKI PARK NARODOWY Quick edit Valid - stable 2022-08-11 PL14197
euProtectedAreaCode.PL14316 KRAJKOWO Quick edit Valid - stable 2022-08-11 PL14316
euProtectedAreaCode.PL145161 S?OTWINA Quick edit Valid - stable 2022-08-11 PL145161
euProtectedAreaCode.PL145162 SMOLARY Quick edit Valid - stable 2022-08-11 PL145162
euProtectedAreaCode.PL145163 SMOLNIK Quick edit Valid - stable 2022-08-11 PL145163
euProtectedAreaCode.PL145165 SOKÓLE Quick edit Valid - stable 2022-08-11 PL145165
euProtectedAreaCode.PL145166 SO?OKIJA Quick edit Valid - stable 2022-08-11 PL145166
euProtectedAreaCode.PL145167 SOSNY Quick edit Valid - stable 2022-08-11 PL145167
euProtectedAreaCode.PL145168 SOSNY TABORSKIE Quick edit Valid - stable 2022-08-11 PL145168
euProtectedAreaCode.PL145171 SO?NICA Quick edit Valid - stable 2022-08-11 PL145171
euProtectedAreaCode.PL145172 SPA?A Quick edit Valid - stable 2022-08-11 PL145172
euProtectedAreaCode.PL145173 STANISZEWSKIE ZDROJE Quick edit Valid - stable 2022-08-11 PL145173
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?