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 137,421 to 137,440.First6,8686,8696,8706,8716,8726,8736,8746,875Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKENRI157 RIVER WANDLE Quick edit Valid - stable 2025-01-29 UKENRI157
euProtectedAreaCode.UKENRI16 RIVER BLACKWATER HAMPSHIRE Quick edit Valid - stable 2025-01-29 UKENRI16
euProtectedAreaCode.UKENRI17 RIVER THAMES Quick edit Valid - stable 2025-01-29 UKENRI17
euProtectedAreaCode.UKENRI18 RIVER RAY WILTSHIRE Quick edit Valid - stable 2025-01-29 UKENRI18
euProtectedAreaCode.UKENRI19 LANGFORD BROOK Quick edit Valid - stable 2025-01-29 UKENRI19
euProtectedAreaCode.UKENRI2 RIVER EDEN Quick edit Valid - stable 2025-01-29 UKENRI2
euProtectedAreaCode.UKENRI23 RIVER BURE Quick edit Valid - stable 2025-01-29 UKENRI23
euProtectedAreaCode.UKENRI24 RIVER ANT Quick edit Valid - stable 2025-01-29 UKENRI24
euProtectedAreaCode.UKENRI29 RIVER NENE Quick edit Valid - stable 2025-01-29 UKENRI29
euProtectedAreaCode.UKENRI31 LOUTH CANAL Quick edit Valid - stable 2025-01-29 UKENRI31
euProtectedAreaCode.UKENRI33 RIVER FOSS Quick edit Valid - stable 2025-01-29 UKENRI33
euProtectedAreaCode.UKENRI34 RIVER LOSTOCK Quick edit Valid - stable 2025-01-29 UKENRI34
euProtectedAreaCode.UKENRI35 RIVER EHEN Quick edit Valid - stable 2025-01-29 UKENRI35
euProtectedAreaCode.UKENRI36 RIVER YARROW Quick edit Valid - stable 2025-01-29 UKENRI36
euProtectedAreaCode.UKENRI37 RIVER EREWASH AND EREWASH CANAL Quick edit Valid - stable 2025-01-29 UKENRI37
euProtectedAreaCode.UKENRI38 RIVER TEME Quick edit Valid - stable 2025-01-29 UKENRI38
euProtectedAreaCode.UKENRI4 RIVER RIBBLE Quick edit Valid - stable 2025-01-29 UKENRI4
euProtectedAreaCode.UKENRI41 RIVERS IDLE MAUN MEDEN AND RYTON Quick edit Valid - stable 2025-01-29 UKENRI41
euProtectedAreaCode.UKENRI42 BOW BROOK Quick edit Valid - stable 2025-01-29 UKENRI42
euProtectedAreaCode.UKENRI43 RIVER LEADON Quick edit Valid - stable 2025-01-29 UKENRI43
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?