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
22 Nov 2024
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

138,317 concepts found, displaying 135,201 to 135,220.First6,7576,7586,7596,7606,7616,7626,7636,764Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SIDRZ8236 RECICA V-1 -VR-1-81 Quick edit Valid - stable 2025-01-29 SIDRZ8236
euProtectedAreaCode.SIDRZ84 POD VRHMI Quick edit Valid - stable 2025-01-29 SIDRZ84
euProtectedAreaCode.SIDRZ8401 KOSNICA Quick edit Valid - stable 2025-01-29 SIDRZ8401
euProtectedAreaCode.SIDRZ8408 VODNJAK G -MEDLOG Quick edit Valid - stable 2025-01-29 SIDRZ8408
euProtectedAreaCode.SIDRZ8410 TREMERJE M-1-93 Quick edit Valid - stable 2025-01-29 SIDRZ8410
euProtectedAreaCode.SIDRZ8411 GABROVKA SPODNJA Quick edit Valid - stable 2025-01-29 SIDRZ8411
euProtectedAreaCode.SIDRZ85 PRI BRDU-OCIZLA Quick edit Valid - stable 2025-01-29 SIDRZ85
euProtectedAreaCode.SIDRZ8551 BREG Quick edit Valid - stable 2025-01-29 SIDRZ8551
euProtectedAreaCode.SIDRZ86 PRI KORITIH Quick edit Valid - stable 2025-01-29 SIDRZ86
euProtectedAreaCode.SIDRZ87 SLIVJE Quick edit Valid - stable 2025-01-29 SIDRZ87
euProtectedAreaCode.SIDRZ88 TRZIC Quick edit Valid - stable 2025-01-29 SIDRZ88
euProtectedAreaCode.SIDRZ89 VELIKA REBER I Quick edit Valid - stable 2025-01-29 SIDRZ89
euProtectedAreaCode.SIDRZ91 VELIKA REBER III Quick edit Valid - stable 2025-01-29 SIDRZ91
euProtectedAreaCode.SIDRZ93 VRTICE-ARTVIZE Quick edit Valid - stable 2025-01-29 SIDRZ93
euProtectedAreaCode.SIDRZ94 ZAGRAD-VODOHRAN Quick edit Valid - stable 2025-01-29 SIDRZ94
euProtectedAreaCode.SIDRZ95 ZATREB-GLOBOKI POTOK Quick edit Valid - stable 2025-01-29 SIDRZ95
euProtectedAreaCode.SIDRZ96 RIZANA Quick edit Valid - stable 2025-01-29 SIDRZ96
euProtectedAreaCode.SILK-SI1128VT VTJ BLEJSKO JEZERO Quick edit Valid - stable 2025-01-29 SILK-SI1128VT
euProtectedAreaCode.SILK-SI112VT3 VTJ BOHINJSKO JEZERO Quick edit Valid - stable 2025-01-29 SILK-SI112VT3
euProtectedAreaCode.SILK-SI141VT2 VTJ CERKNISKO JEZERO Quick edit Valid - stable 2025-01-29 SILK-SI141VT2
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?