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,341 to 135,360.First6,7646,7656,7666,7676,7686,7696,7706,771Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SIOBC2046 RODINE Quick edit Valid - stable 2025-01-29 SIOBC2046
euProtectedAreaCode.SIOBC2047 ZAVRSNICA Quick edit Valid - stable 2025-01-29 SIOBC2047
euProtectedAreaCode.SIOBC2050 LJUBELJ Quick edit Valid - stable 2025-01-29 SIOBC2050
euProtectedAreaCode.SIOBC2051 SMOLEKAR Quick edit Valid - stable 2025-01-29 SIOBC2051
euProtectedAreaCode.SIOBC2052 LAJBA Quick edit Valid - stable 2025-01-29 SIOBC2052
euProtectedAreaCode.SIOBC2053 CRNI GOZD Quick edit Valid - stable 2025-01-29 SIOBC2053
euProtectedAreaCode.SIOBC2054 ZEGNANI STUDENEC Quick edit Valid - stable 2025-01-29 SIOBC2054
euProtectedAreaCode.SIOBC2057 BREZJE Quick edit Valid - stable 2025-01-29 SIOBC2057
euProtectedAreaCode.SIOBC2058 HUDI GRABEN Quick edit Valid - stable 2025-01-29 SIOBC2058
euProtectedAreaCode.SIOBC2059 PALOVICE Quick edit Valid - stable 2025-01-29 SIOBC2059
euProtectedAreaCode.SIOBC2060 RAVNE Quick edit Valid - stable 2025-01-29 SIOBC2060
euProtectedAreaCode.SIOBC2062 VETERNO Quick edit Valid - stable 2025-01-29 SIOBC2062
euProtectedAreaCode.SIOBC2063 GOZD Quick edit Valid - stable 2025-01-29 SIOBC2063
euProtectedAreaCode.SIOBC2064 SENICNO Quick edit Valid - stable 2025-01-29 SIOBC2064
euProtectedAreaCode.SIOBC2065 JELENDOL Quick edit Valid - stable 2025-01-29 SIOBC2065
euProtectedAreaCode.SIOBC2066 LOM 1 Quick edit Valid - stable 2025-01-29 SIOBC2066
euProtectedAreaCode.SIOBC2067 LOM 2 Quick edit Valid - stable 2025-01-29 SIOBC2067
euProtectedAreaCode.SIOBC2070 RADOVNA Quick edit Valid - stable 2025-01-29 SIOBC2070
euProtectedAreaCode.SIOBC2080 PODTABOR-DUPLJE Quick edit Valid - stable 2025-01-29 SIOBC2080
euProtectedAreaCode.SIOBC2081 VRTINA PODTABOR Quick edit Valid - stable 2025-01-29 SIOBC2081
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?