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,481 to 137,500.First6,8716,8726,8736,8746,8756,8766,8776,878Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKENRI92 RIVER KENT Quick edit Valid - stable 2025-01-29 UKENRI92
euProtectedAreaCode.UKENRI93 RIVER CALDER Quick edit Valid - stable 2025-01-29 UKENRI93
euProtectedAreaCode.UKENRI94 RIVER IRWELL Quick edit Valid - stable 2025-01-29 UKENRI94
euProtectedAreaCode.UKENRI95 RIVER ALT Quick edit Valid - stable 2025-01-29 UKENRI95
euProtectedAreaCode.UKENRI96 RIVER WANSBECK AND AMENITY LAKE Quick edit Valid - stable 2025-01-29 UKENRI96
euProtectedAreaCode.UKENRI97 RIVER DERWENT NORTHUMBRIA Quick edit Valid - stable 2025-01-29 UKENRI97
euProtectedAreaCode.UKENRI99 RIVER TORNE Quick edit Valid - stable 2025-01-29 UKENRI99
euProtectedAreaCode.UKENSO_CM109 RIVER ARUN Quick edit Valid - stable 2025-01-29 UKENSO_CM109
euProtectedAreaCode.UKENSO_CM110 RIVER ITCHEN HAMPSH Quick edit Valid - stable 2025-01-29 UKENSO_CM110
euProtectedAreaCode.UKENSO_CM112 PAGHAM HARBOUR Quick edit Valid - stable 2025-01-29 UKENSO_CM112
euProtectedAreaCode.UKENSO_CM123 HAMBLE ESTUARY Quick edit Valid - stable 2025-01-29 UKENSO_CM123
euProtectedAreaCode.UKENSO_CM126 LITTLE STOUR Quick edit Valid - stable 2025-01-29 UKENSO_CM126
euProtectedAreaCode.UKENSO_CM128 RIVER ROTHER WEST Quick edit Valid - stable 2025-01-29 UKENSO_CM128
euProtectedAreaCode.UKENSO_CM13 RIVER TEST Quick edit Valid - stable 2025-01-29 UKENSO_CM13
euProtectedAreaCode.UKENSO_CM14 RIVER GREAT STOUR Quick edit Valid - stable 2025-01-29 UKENSO_CM14
euProtectedAreaCode.UKENSO_CM146 RIVER ADUR EAST CATCHMENT Quick edit Valid - stable 2025-01-29 UKENSO_CM146
euProtectedAreaCode.UKENSO_CM147 RIVER OUSE CATCHMENT Quick edit Valid - stable 2025-01-29 UKENSO_CM147
euProtectedAreaCode.UKENSO_CM56 CHICHESTER HARBOUR Quick edit Valid - stable 2025-01-29 UKENSO_CM56
euProtectedAreaCode.UKENSO_CMLK120 BEWL RESERVOIR CATCHMENT Quick edit Valid - stable 2025-01-29 UKENSO_CMLK120
euProtectedAreaCode.UKENSW_CM115 UPPER BRISTOL AVON Quick edit Valid - stable 2025-01-29 UKENSW_CM115
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?