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,256 concepts found, displaying 2,241 to 2,260.First109110111112113114115116Last
Id Label Status Status Modified Notation
euProtectedAreaCode.BG4ST700R1025 ELESHNITSA ST1025 Quick edit Deprecated 2025-11-04 BG4ST700R1025
euProtectedAreaCode.BG4ST800R016 TREKLYANSKA ST016 Quick edit Deprecated 2025-11-04 BG4ST800R016
euProtectedAreaCode.BGCSACL13 CATCHEMENT OF BLACK SEA COASTAL LINE Quick edit Valid - stable 2025-01-29 BGCSACL13
euProtectedAreaCode.BGCSARI01 CATCHEMENT OF ARDA RIVER Quick edit Valid - stable 2025-01-29 BGCSARI01
euProtectedAreaCode.BGCSARI02 CATCHEMENT OF VIT RIVER Quick edit Valid - stable 2025-01-29 BGCSARI02
euProtectedAreaCode.BGCSARI03 CATCHEMENT OF DANUBE RIVER Quick edit Valid - stable 2025-01-29 BGCSARI03
euProtectedAreaCode.BGCSARI04 CATCHEMENT OF ISKAR RIVER Quick edit Valid - stable 2025-01-29 BGCSARI04
euProtectedAreaCode.BGCSARI05 CATCHEMENT OF KAMTCHIA RIVER Quick edit Valid - stable 2025-01-29 BGCSARI05
euProtectedAreaCode.BGCSARI06 CATCHEMENT OF MARITZA RIVER Quick edit Valid - stable 2025-01-29 BGCSARI06
euProtectedAreaCode.BGCSARI07 CATCHEMENT OF OGOSTA RIVER Quick edit Valid - stable 2025-01-29 BGCSARI07
euProtectedAreaCode.BGCSARI08 CATCHEMENT OF OSAM RIVER Quick edit Valid - stable 2025-01-29 BGCSARI08
euProtectedAreaCode.BGCSARI09 CATCHEMENT OF PROVADIJSKA I DEVNENSKA RIVER Quick edit Valid - stable 2025-01-29 BGCSARI09
euProtectedAreaCode.BGCSARI10 CATCHEMENT OF RUSENSKI LOM RIVER Quick edit Valid - stable 2025-01-29 BGCSARI10
euProtectedAreaCode.BGCSARI11 CATCHEMENT OF STRUMA RIVER Quick edit Valid - stable 2025-01-29 BGCSARI11
euProtectedAreaCode.BGCSARI12 CATCHEMENT OF TUNDJA RIVER Quick edit Valid - stable 2025-01-29 BGCSARI12
euProtectedAreaCode.BGCSARI14 CATCHEMENT OF YANTRA RIVER Quick edit Valid - stable 2025-01-29 BGCSARI14
euProtectedAreaCode.BGNVZ NITRATES VULNERABLE ZONE Quick edit Valid - experimental 2025-01-29 BGNVZ
euProtectedAreaCode.BGSACL13 BLACK SEA COASTAL LINE Quick edit Valid - stable 2025-01-29 BGSACL13
euProtectedAreaCode.BGSARI01 ARDA RIVER Quick edit Valid - stable 2025-01-29 BGSARI01
euProtectedAreaCode.BGSARI02 VIT RIVER Quick edit Valid - stable 2025-01-29 BGSARI02
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?