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,641 to 96,660.First4,8294,8304,8314,8324,8334,8344,8354,836Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL177753 KARTUSKI Quick edit Valid - stable 2022-08-11 PL177753
euProtectedAreaCode.PL177754 LIPUSKI Quick edit Valid - stable 2022-08-11 PL177754
euProtectedAreaCode.PL177755 NADMORSKI Quick edit Valid - stable 2022-08-11 PL177755
euProtectedAreaCode.PL177756 BORÓW TUCHOLSKICH Quick edit Valid - stable 2022-08-11 PL177756
euProtectedAreaCode.PL177757 DOLINY ?EBY Quick edit Valid - stable 2022-08-11 PL177757
euProtectedAreaCode.PL177758 DOLINY RADUNI Quick edit Valid - stable 2022-08-11 PL177758
euProtectedAreaCode.PL177759 DOLINY WIERZYCY Quick edit Valid - stable 2022-08-11 PL177759
euProtectedAreaCode.PL177760 DOLINY WIETCISY Quick edit Valid - stable 2022-08-11 PL177760
euProtectedAreaCode.PL177761 PRADOLINY REDY-?EBY Quick edit Valid - stable 2022-08-11 PL177761
euProtectedAreaCode.PL177763 ?U?AW GDA?SKICH Quick edit Valid - stable 2022-08-11 PL177763
euProtectedAreaCode.PL177764 WYSPY SOBIESZEWSKIEJ Quick edit Valid - stable 2022-08-11 PL177764
euProtectedAreaCode.PL177765 OTOMI?SKI Quick edit Valid - stable 2022-08-11 PL177765
euProtectedAreaCode.PL177766 POLASZKOWSKI Quick edit Valid - stable 2022-08-11 PL177766
euProtectedAreaCode.PL177767 PRZYWIDZKI Quick edit Valid - stable 2022-08-11 PL177767
euProtectedAreaCode.PL177768 CHMIELNICKO-SZYD?OWSKI Quick edit Valid - stable 2022-08-11 PL177768
euProtectedAreaCode.PL177769 KONECKO-?OPUSZNIA?SKI Quick edit Valid - stable 2022-08-11 PL177769
euProtectedAreaCode.PL177772 SOLECKO-PACANOWSKI Quick edit Valid - stable 2022-08-11 PL177772
euProtectedAreaCode.PL177773 DOLINA GOLDAPY I W?GORAPY Quick edit Valid - stable 2022-08-11 PL177773
euProtectedAreaCode.PL177774 DOLINY LEGI Quick edit Valid - stable 2022-08-11 PL177774
euProtectedAreaCode.PL177776 JEZIOR OLECKICH Quick edit Valid - stable 2022-08-11 PL177776
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?