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,041 to 96,060.First4,7994,8004,8014,8024,8034,8044,8054,806Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL145174 STARA BUCZYNA W RAKOWIE Quick edit Valid - stable 2022-08-11 PL145174
euProtectedAreaCode.PL145175 STARA D?BINA Quick edit Valid - stable 2022-08-11 PL145175
euProtectedAreaCode.PL145176 STARA RUDA Quick edit Valid - stable 2022-08-11 PL145176
euProtectedAreaCode.PL145177 STARE BIELE Quick edit Valid - stable 2022-08-11 PL145177
euProtectedAreaCode.PL145178 STARE MODRZEWIE Quick edit Valid - stable 2022-08-11 PL145178
euProtectedAreaCode.PL145179 STARODRZEW DOBIESZY?SKI Quick edit Valid - stable 2022-08-11 PL145179
euProtectedAreaCode.PL145180 STARODRZEW LUBOCHNIA?SKI Quick edit Valid - stable 2022-08-11 PL145180
euProtectedAreaCode.PL145181 STARODRZEW SZYNDZIELSKI Quick edit Valid - stable 2022-08-11 PL145181
euProtectedAreaCode.PL145182 STARO?YN Quick edit Valid - stable 2022-08-11 PL145182
euProtectedAreaCode.PL145183 STARY PRZYLEP Quick edit Valid - stable 2022-08-11 PL145183
euProtectedAreaCode.PL145184 STARZYNA Quick edit Valid - stable 2022-08-11 PL145184
euProtectedAreaCode.PL145185 STASIN Quick edit Valid - stable 2022-08-11 PL145185
euProtectedAreaCode.PL145186 STAW NOWOKU?NICKI Quick edit Valid - stable 2022-08-11 PL145186
euProtectedAreaCode.PL145187 STAWINOGA Quick edit Valid - stable 2022-08-11 PL145187
euProtectedAreaCode.PL145188 STAWISKA Quick edit Valid - stable 2022-08-11 PL145188
euProtectedAreaCode.PL145189 STAWSKA GÓRA Quick edit Valid - stable 2022-08-11 PL145189
euProtectedAreaCode.PL145190 STAWY BROSZKOWSKIE Quick edit Valid - stable 2022-08-11 PL145190
euProtectedAreaCode.PL145191 STERCZÓW-?CIANKA Quick edit Valid - stable 2022-08-11 PL145191
euProtectedAreaCode.PL145192 STERDY? Quick edit Valid - stable 2022-08-11 PL145192
euProtectedAreaCode.PL145193 STOK SZYNDZIELNI Quick edit Valid - stable 2022-08-11 PL145193
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?