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 95,881 to 95,900.First4,7914,7924,7934,7944,7954,7964,7974,798Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL122876 OBORY- W WERYFIKACJI Quick edit Valid - stable 2022-08-11 PL122876
euProtectedAreaCode.PL122877 OCHOJEC Quick edit Valid - stable 2022-08-11 PL122877
euProtectedAreaCode.PL122878 ODRZYSKO Quick edit Valid - stable 2022-08-11 PL122878
euProtectedAreaCode.PL122879 OKALEWO Quick edit Valid - stable 2022-08-11 PL122879
euProtectedAreaCode.PL122881 OLBINA Quick edit Valid - stable 2022-08-11 PL122881
euProtectedAreaCode.PL122882 OLESZNO Quick edit Valid - stable 2022-08-11 PL122882
euProtectedAreaCode.PL122883 OLSZA KOSA W ST??NICY Quick edit Valid - stable 2022-08-11 PL122883
euProtectedAreaCode.PL122884 OLSZANKA Quick edit Valid - stable 2022-08-11 PL122884
euProtectedAreaCode.PL122885 OLSZYNA ??GOWA W KALNICY Quick edit Valid - stable 2022-08-11 PL122885
euProtectedAreaCode.PL122886 OLSZYNA ?YCZY?SKA Quick edit Valid - stable 2022-08-11 PL122886
euProtectedAreaCode.PL122887 OLSZYNKA GROCHOWSKA Quick edit Valid - stable 2022-08-11 PL122887
euProtectedAreaCode.PL122888 OLSZYNY Quick edit Valid - stable 2022-08-11 PL122888
euProtectedAreaCode.PL122889 OLSZYNY NIEZGODZKIE Quick edit Valid - stable 2022-08-11 PL122889
euProtectedAreaCode.PL122890 OLSZYNY OSTROWSKIE Quick edit Valid - stable 2022-08-11 PL122890
euProtectedAreaCode.PL122891 OMELNO Quick edit Valid - stable 2022-08-11 PL122891
euProtectedAreaCode.PL122894 OPALONKI Quick edit Valid - stable 2022-08-11 PL122894
euProtectedAreaCode.PL122895 ORLE NAD JEZIOREM DU?YM Quick edit Valid - stable 2022-08-11 PL122895
euProtectedAreaCode.PL122896 OSETNICA Quick edit Valid - stable 2022-08-11 PL122896
euProtectedAreaCode.PL122898 OSTOJA BOBRÓW MARYCHA Quick edit Valid - stable 2022-08-11 PL122898
euProtectedAreaCode.PL122899 OSTOJA BOBRÓW NA RZECE PAS??CE Quick edit Valid - stable 2022-08-11 PL122899
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?