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 97,421 to 97,440.First4,8684,8694,8704,8714,8724,8734,8744,875Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL555562757 WYSOCZYZNY ELBL?SKIEJ - WSCHÓD Quick edit Valid - stable 2022-08-11 PL555562757
euProtectedAreaCode.PL555562758 RZEKI SZKARPAWY Quick edit Valid - stable 2022-08-11 PL555562758
euProtectedAreaCode.PL555562760 BORY BOGUMI?OWSKIE Quick edit Valid - stable 2022-08-11 PL555562760
euProtectedAreaCode.PL555562761 DOLINA SZPROTAWKI Quick edit Valid - stable 2022-08-11 PL555562761
euProtectedAreaCode.PL555562762 DOLINA BOBRU Quick edit Valid - stable 2022-08-11 PL555562762
euProtectedAreaCode.PL555562763 DOLINA SYMSARNY Quick edit Valid - stable 2022-08-11 PL555562763
euProtectedAreaCode.PL555562764 JEZIOR LEGI?SKO-MR?GOWSKICH Quick edit Valid - stable 2022-08-11 PL555562764
euProtectedAreaCode.PL555562765 DOLINY ELMY Quick edit Valid - stable 2022-08-11 PL555562765
euProtectedAreaCode.PL555562766 DOLINA WARTY I DOLNEJ NOTECI Quick edit Valid - stable 2022-08-11 PL555562766
euProtectedAreaCode.PL555562767 JEZIOR RAJGRODZKICH Quick edit Valid - stable 2022-08-11 PL555562767
euProtectedAreaCode.PL555562768 DOLINY DOLNEJ ?YNY Quick edit Valid - stable 2022-08-11 PL555562768
euProtectedAreaCode.PL555562769 GORZYCKO Quick edit Valid - stable 2022-08-11 PL555562769
euProtectedAreaCode.PL555562770 JEZIORA O?WIN Quick edit Valid - stable 2022-08-11 PL555562770
euProtectedAreaCode.PL555562771 NARIE?SKI Quick edit Valid - stable 2022-08-11 PL555562771
euProtectedAreaCode.PL555562773 POJEZIERZA I?AWSKIEGO - CZ??? A I B Quick edit Valid - stable 2022-08-11 PL555562773
euProtectedAreaCode.PL555562774 OTULINY MAZURSKIEGO PARKU KRAJOBRAZOWEGO - WSCHÓD Quick edit Valid - stable 2022-08-11 PL555562774
euProtectedAreaCode.PL555562775 WZGÓRZ DYLEWSKICH Quick edit Valid - stable 2022-08-11 PL555562775
euProtectedAreaCode.PL555562776 ZIELU?SKO-RZ?GNOWSKI Quick edit Valid - stable 2022-08-11 PL555562776
euProtectedAreaCode.PL555562777 SIERADOWICKI Quick edit Valid - stable 2022-08-11 PL555562777
euProtectedAreaCode.PL555562778 DOLINA SKRWY LEWEJ Quick edit Valid - stable 2022-08-11 PL555562778
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?