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,801 to 96,820.First4,8374,8384,8394,8404,8414,8424,8434,844Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL31677 JEZIORO ??TOWSKIE I OKOLICE K?PIC Quick edit Valid - stable 2022-08-11 PL31677
euProtectedAreaCode.PL31679 OKOLICE JEZIOR KR?PSKO I SZCZYTNO Quick edit Valid - stable 2022-08-11 PL31679
euProtectedAreaCode.PL31680 PAS POBRZE?A NA WSCHÓD OD USTKI Quick edit Valid - stable 2022-08-11 PL31680
euProtectedAreaCode.PL31683 ?RÓDLISKOWY OBSZAR BRDY I WIEPRZY NA WSCHÓD OD MIASTKA Quick edit Valid - stable 2022-08-11 PL31683
euProtectedAreaCode.PL31684 JELENIOWSKO-STASZOWSKI Quick edit Valid - stable 2022-08-11 PL31684
euProtectedAreaCode.PL31686 GÓRY BARDZKIE I SOWIE Quick edit Valid - stable 2022-08-11 PL31686
euProtectedAreaCode.PL31687 GÓRY BYSTRZYCKIE I ORLICKIE Quick edit Valid - stable 2022-08-11 PL31687
euProtectedAreaCode.PL31689 KOPU?Y CHE?MCA Quick edit Valid - stable 2022-08-11 PL31689
euProtectedAreaCode.PL31691 DRUMLINY ZBÓJE?SKIE Quick edit Valid - stable 2022-08-11 PL31691
euProtectedAreaCode.PL31692 JEZIORO G?USZY?SKIE Quick edit Valid - stable 2022-08-11 PL31692
euProtectedAreaCode.PL31693 JEZIORO MODZEROWSKIE Quick edit Valid - stable 2022-08-11 PL31693
euProtectedAreaCode.PL31694 JEZIORO SK?PSKIE Quick edit Valid - stable 2022-08-11 PL31694
euProtectedAreaCode.PL31695 NIZINY CIECHOCI?SKIEJ Quick edit Valid - stable 2022-08-11 PL31695
euProtectedAreaCode.PL31696 ?RÓD?A SKRWY Quick edit Valid - stable 2022-08-11 PL31696
euProtectedAreaCode.PL31697 BORY DOLNO?L?SKIE Quick edit Valid - stable 2022-08-11 PL31697
euProtectedAreaCode.PL31700 WZNIESIENIA ZIELONOGÓRSKIE Quick edit Valid - stable 2022-08-11 PL31700
euProtectedAreaCode.PL3210303218000002 KAP CHOTOWA Quick edit Deprecated - retired 2022-08-11 PL3210303218000002
euProtectedAreaCode.PL3210304218000001 KAP JALOWCE Quick edit Deprecated - retired 2022-08-11 PL3210304218000001
euProtectedAreaCode.PL3210802218000013 CZYSTE - GRODZISKO DOLNE Quick edit Valid - stable 2022-08-11 PL3210802218000013
euProtectedAreaCode.PL3211107218000003 KAP RZEMIEN Quick edit Deprecated - retired 2022-08-11 PL3211107218000003
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?