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,461 to 97,480.First4,8704,8714,8724,8734,8744,8754,8764,877Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL555562804 WYSOCZYZNY ELBL?SKIEJ - ZACHÓD Quick edit Valid - stable 2022-08-11 PL555562804
euProtectedAreaCode.PL555562805 C BARLINEK Quick edit Valid - stable 2022-08-11 PL555562805
euProtectedAreaCode.PL555562806 DOLINA PROSNY Quick edit Valid - stable 2022-08-11 PL555562806
euProtectedAreaCode.PL555562807 S?UBICKA DOLINA Quick edit Valid - stable 2022-08-11 PL555562807
euProtectedAreaCode.PL555562808 ZACHODNIEGO POGÓRZA WI?NICKIEGO Quick edit Valid - stable 2022-08-11 PL555562808
euProtectedAreaCode.PL555562809 NA PO?UDNIOWY WSCHÓD OD JEZIORA BIELSKO Quick edit Valid - stable 2022-08-11 PL555562809
euProtectedAreaCode.PL555562810 W?OSZCZOWSKO-J?DRZEJOWSKI Quick edit Valid - stable 2022-08-11 PL555562810
euProtectedAreaCode.PL555562811 DOLINY RZEKI NIDY I SZKOTÓWKI Quick edit Valid - stable 2022-08-11 PL555562811
euProtectedAreaCode.PL555562812 PUSZCZY ROMINCKIEJ Quick edit Valid - stable 2022-08-11 PL555562812
euProtectedAreaCode.PL555562813 MI?DZYRZECZE SKRWY I WKRY Quick edit Valid - stable 2022-08-11 PL555562813
euProtectedAreaCode.PL555562814 JEZIORA MIELNO Quick edit Valid - stable 2022-08-11 PL555562814
euProtectedAreaCode.PL555562815 SPYCHOWSKI Quick edit Valid - stable 2022-08-11 PL555562815
euProtectedAreaCode.PL555562816 OTMUCHOWSKO-NYSKI Quick edit Valid - stable 2022-08-11 PL555562816
euProtectedAreaCode.PL555562818 B MY?LIBÓRZ Quick edit Valid - stable 2022-08-11 PL555562818
euProtectedAreaCode.PL555562819 WSCHODNIE OKOLICE LUBSKA Quick edit Valid - stable 2022-08-11 PL555562819
euProtectedAreaCode.PL555562820 DOLINY WIDAWKI Quick edit Valid - stable 2022-08-11 PL555562820
euProtectedAreaCode.PL555562821 DOLINA ILANKI Quick edit Valid - stable 2022-08-11 PL555562821
euProtectedAreaCode.PL555562822 GOSTYNI?SKO-G?BI?SKI Quick edit Valid - stable 2022-08-11 PL555562822
euProtectedAreaCode.PL555562823 LASÓW TABORSKICH Quick edit Valid - stable 2022-08-11 PL555562823
euProtectedAreaCode.PL555562825 DOLINY PI?AWY Quick edit Valid - stable 2022-08-11 PL555562825
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?