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,001 to 2,020.First979899100101102103104Last
Id Label Status Status Modified Notation
euProtectedAreaCode.BG3FSWMA905R198 TOPLI DERE RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA905R198
euProtectedAreaCode.BG3FSWMA906R198 ABLANITSA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWMA906R198
euProtectedAreaCode.BG3FSWTU100R002 TUNDZA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU100R002
euProtectedAreaCode.BG3FSWTU100R003 MANASTIRSKA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU100R003
euProtectedAreaCode.BG3FSWTU100R004 MELNISKA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU100R004
euProtectedAreaCode.BG3FSWTU135R005 TUNDZA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU135R005
euProtectedAreaCode.BG3FSWTU200R007 KALNITSA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU200R007
euProtectedAreaCode.BG3FSWTU200R008 SINAPOVSKA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU200R008
euProtectedAreaCode.BG3FSWTU500R012 POPOVSKA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU500R012
euProtectedAreaCode.BG3FSWTU500R016 TUNDZA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU500R016
euProtectedAreaCode.BG3FSWTU570R066 TUNDZA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU570R066
euProtectedAreaCode.BG3FSWTU570R067 TUNDZA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU570R067
euProtectedAreaCode.BG3FSWTU600R062 MOCKURITSA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU600R062
euProtectedAreaCode.BG3FSWTU700R032 TUNDZA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU700R032
euProtectedAreaCode.BG3FSWTU700R035 GOLYAMATA REKA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU700R035
euProtectedAreaCode.BG3FSWTU900R042 TUNDZA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU900R042
euProtectedAreaCode.BG3FSWTU900R045 SELCHANSKA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU900R045
euProtectedAreaCode.BG3FSWTU900R046 ENINSKA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU900R046
euProtectedAreaCode.BG3FSWTU900R052 LESHNITSA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU900R052
euProtectedAreaCode.BG3FSWTU900R053 GABROVNITSA RIVER Quick edit Valid - stable 2025-01-29 BG3FSWTU900R053
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?