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,361 to 135,380.First6,7656,7666,7676,7686,7696,7706,7716,772Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SIOBC2100 PRI CERKVI-DRAZGOSE Quick edit Valid - stable 2025-01-29 SIOBC2100
euProtectedAreaCode.SIOBC2101 NA PECEH-DRAZGOSE Quick edit Valid - stable 2025-01-29 SIOBC2101
euProtectedAreaCode.SIOBC2103 SORISKA PLANINA Quick edit Valid - stable 2025-01-29 SIOBC2103
euProtectedAreaCode.SIOBC2105 POTOK Quick edit Valid - stable 2025-01-29 SIOBC2105
euProtectedAreaCode.SIOBC2106 DAVCA Quick edit Valid - stable 2025-01-29 SIOBC2106
euProtectedAreaCode.SIOBC2107 SORICA 2 Quick edit Valid - stable 2025-01-29 SIOBC2107
euProtectedAreaCode.SIOBC2110 ROBIDNICA-LAZE-LAJSE-KRNICA Quick edit Valid - stable 2025-01-29 SIOBC2110
euProtectedAreaCode.SIOBC2114 GOLICA-SELCA Quick edit Valid - stable 2025-01-29 SIOBC2114
euProtectedAreaCode.SIOBC2115 PRSTENICE Quick edit Valid - stable 2025-01-29 SIOBC2115
euProtectedAreaCode.SIOBC2116 PODLONK Quick edit Valid - stable 2025-01-29 SIOBC2116
euProtectedAreaCode.SIOBC2119 SELCA Quick edit Valid - stable 2025-01-29 SIOBC2119
euProtectedAreaCode.SIOBC2120 TOPOLJE-SELCE Quick edit Valid - stable 2025-01-29 SIOBC2120
euProtectedAreaCode.SIOBC2123 DOLENJA VAS 2 Quick edit Valid - stable 2025-01-29 SIOBC2123
euProtectedAreaCode.SIOBC2124 PLENSAK Quick edit Valid - stable 2025-01-29 SIOBC2124
euProtectedAreaCode.SIOBC2126 KALISE Quick edit Valid - stable 2025-01-29 SIOBC2126
euProtectedAreaCode.SIOBC2150 LUCINE Quick edit Valid - stable 2025-01-29 SIOBC2150
euProtectedAreaCode.SIOBC2151 SOVODENJ Quick edit Valid - stable 2025-01-29 SIOBC2151
euProtectedAreaCode.SIOBC2152 JAKAPONEC-TREBIJA Quick edit Valid - stable 2025-01-29 SIOBC2152
euProtectedAreaCode.SIOBC2156 DOBRAVSCE Quick edit Valid - stable 2025-01-29 SIOBC2156
euProtectedAreaCode.SIOBC2158 ZABJA VAS Quick edit Valid - stable 2025-01-29 SIOBC2158
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?