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,621 to 96,640.First4,8284,8294,8304,8314,8324,8334,8344,835Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL177713 RZEKI LIWY (WOJ. POMORSKIE) Quick edit Valid - stable 2022-08-11 PL177713
euProtectedAreaCode.PL177714 RZEKI LIWY (WOJ. WARMI?SKO-MAZURSKIE) Quick edit Valid - stable 2022-08-11 PL177714
euProtectedAreaCode.PL177717 RZEKI NOGAT (WOJ. WARMI?SKO-MAZURSKIE) Quick edit Valid - stable 2022-08-11 PL177717
euProtectedAreaCode.PL177718 RZEKI NOGAT (WOJ. POMORSKIE) Quick edit Valid - stable 2022-08-11 PL177718
euProtectedAreaCode.PL177721 ZAWORY Quick edit Valid - stable 2022-08-11 PL177721
euProtectedAreaCode.PL177722 WZGÓRZA OSTRZESZOWSKIE I KOTLINA ODOLANOWSKA (WOJ. DOLNO?L?SKIE) Quick edit Valid - stable 2022-08-11 PL177722
euProtectedAreaCode.PL177724 DO?HOBYCZOWSKI Quick edit Valid - stable 2022-08-11 PL177724
euProtectedAreaCode.PL177732 BRATUCICKI Quick edit Valid - stable 2022-08-11 PL177732
euProtectedAreaCode.PL177734 JASTRZ?BSKO-?D?ARSKI Quick edit Valid - stable 2022-08-11 PL177734
euProtectedAreaCode.PL177735 KOSZYCKO-OPATOWIECKI Quick edit Valid - stable 2022-08-11 PL177735
euProtectedAreaCode.PL177736 MIECHOWSKO-DZIA?OSZYCKI Quick edit Valid - stable 2022-08-11 PL177736
euProtectedAreaCode.PL177737 DOLINY WIS?Y Quick edit Valid - stable 2022-08-11 PL177737
euProtectedAreaCode.PL177739 POGÓRZA CI??KOWICKIEGO (WOJ. MA?OPOLSKIE) Quick edit Valid - stable 2022-08-11 PL177739
euProtectedAreaCode.PL177740 WSCHODNIEGO POGÓRZA WI?NICKIEGO Quick edit Valid - stable 2022-08-11 PL177740
euProtectedAreaCode.PL177741 RAD?OWSKO-WIERZCHOS?AWICKI Quick edit Valid - stable 2022-08-11 PL177741
euProtectedAreaCode.PL177742 WARSZAWSKI Quick edit Valid - stable 2022-08-11 PL177742
euProtectedAreaCode.PL177746 RÓWNINY KURPIOWSKIEJ I DOLINY DOLNEJ NARWI Quick edit Valid - stable 2022-08-11 PL177746
euProtectedAreaCode.PL177750 GNIEWSKI Quick edit Valid - stable 2022-08-11 PL177750
euProtectedAreaCode.PL177751 CHOCZEWSKO-SALI?SKI Quick edit Valid - stable 2022-08-11 PL177751
euProtectedAreaCode.PL177752 GOWIDLI?SKI Quick edit Valid - stable 2022-08-11 PL177752
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?