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,361 to 137,380.First6,8656,8666,8676,8686,8696,8706,8716,872Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKENNW_CM151 RIVER WYRE CATCHMENT Quick edit Valid - stable 2025-01-29 UKENNW_CM151
euProtectedAreaCode.UKENNW_CM154 RIVER DARWEN CATCHMENT Quick edit Valid - stable 2025-01-29 UKENNW_CM154
euProtectedAreaCode.UKENNW_CM155 RIVER WEAVER CATCHMENT Quick edit Valid - stable 2025-01-29 UKENNW_CM155
euProtectedAreaCode.UKENNW_CM156 SINDERLAND BROOK CATCHMENT Quick edit Valid - stable 2025-01-29 UKENNW_CM156
euProtectedAreaCode.UKENNW_CM2 RIVER EDEN Quick edit Valid - stable 2025-01-29 UKENNW_CM2
euProtectedAreaCode.UKENNW_CM3 LAKE WINDERMERE Quick edit Valid - stable 2025-01-29 UKENNW_CM3
euProtectedAreaCode.UKENNW_CM35 RIVER EHEN Quick edit Valid - stable 2025-01-29 UKENNW_CM35
euProtectedAreaCode.UKENNW_CM4 RIVER RIBBLE Quick edit Valid - stable 2025-01-29 UKENNW_CM4
euProtectedAreaCode.UKENNW_CM6 RIVER DOUGLAS Quick edit Valid - stable 2025-01-29 UKENNW_CM6
euProtectedAreaCode.UKENNW_CM94 RIVER IRWELL Quick edit Valid - stable 2025-01-29 UKENNW_CM94
euProtectedAreaCode.UKENNW_CM95 RIVER ALT Quick edit Valid - stable 2025-01-29 UKENNW_CM95
euProtectedAreaCode.UKENRI10 RIVER AVON WARWICKSHIRE Quick edit Valid - stable 2025-01-29 UKENRI10
euProtectedAreaCode.UKENRI100 RIVER WYE Quick edit Valid - stable 2025-01-29 UKENRI100
euProtectedAreaCode.UKENRI101 MIDDLE RIVER DERWENT Quick edit Valid - stable 2025-01-29 UKENRI101
euProtectedAreaCode.UKENRI102 RIVER AMBER WESTWOOD ALFRESTON BROOKS Quick edit Valid - stable 2025-01-29 UKENRI102
euProtectedAreaCode.UKENRI103 RIVER SOAR Quick edit Valid - stable 2025-01-29 UKENRI103
euProtectedAreaCode.UKENRI104 RIVER WREAKE Quick edit Valid - stable 2025-01-29 UKENRI104
euProtectedAreaCode.UKENRI105 RIVER SENCE Quick edit Valid - stable 2025-01-29 UKENRI105
euProtectedAreaCode.UKENRI106 RIVER ANKER Quick edit Valid - stable 2025-01-29 UKENRI106
euProtectedAreaCode.UKENRI109 RIVER ARUN Quick edit Valid - stable 2025-01-29 UKENRI109
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?