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,341 to 137,360.First6,8646,8656,8666,8676,8686,8696,8706,871Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKENMI_CM153 RIVERS SOW AND PENK CATCHMENT Quick edit Valid - stable 2025-01-29 UKENMI_CM153
euProtectedAreaCode.UKENMI_CM37 RIVER EREWASH AND ER Quick edit Valid - stable 2025-01-29 UKENMI_CM37
euProtectedAreaCode.UKENMI_CM38 RIVER TEME Quick edit Valid - stable 2025-01-29 UKENMI_CM38
euProtectedAreaCode.UKENMI_CM41 RIVERS IDLE MAUN M Quick edit Valid - stable 2025-01-29 UKENMI_CM41
euProtectedAreaCode.UKENMI_CM42 BOW BROOK Quick edit Valid - stable 2025-01-29 UKENMI_CM42
euProtectedAreaCode.UKENMI_CM43 RIVER LEADON Quick edit Valid - stable 2025-01-29 UKENMI_CM43
euProtectedAreaCode.UKENMI_CM8 RIVER BLYTHE Quick edit Valid - stable 2025-01-29 UKENMI_CM8
euProtectedAreaCode.UKENMI_CM87 RIVER LEAM CATCHMENT Quick edit Valid - stable 2025-01-29 UKENMI_CM87
euProtectedAreaCode.UKENMI_CM9 RIVER ARROW Quick edit Valid - stable 2025-01-29 UKENMI_CM9
euProtectedAreaCode.UKENNE_CM76 RIVER WISKE Quick edit Valid - stable 2025-01-29 UKENNE_CM76
euProtectedAreaCode.UKENNE_CM79 RIVER WEAR Quick edit Valid - stable 2025-01-29 UKENNE_CM79
euProtectedAreaCode.UKENNE_CM80 RIVER SKERNE TEES C Quick edit Valid - stable 2025-01-29 UKENNE_CM80
euProtectedAreaCode.UKENNE_CM96 RIVER WANSBECK AND A Quick edit Valid - stable 2025-01-29 UKENNE_CM96
euProtectedAreaCode.UKENNE_CM97 RIVER DERWENT NORTH Quick edit Valid - stable 2025-01-29 UKENNE_CM97
euProtectedAreaCode.UKENNE_CM98 SEAL SANDS Quick edit Valid - stable 2025-01-29 UKENNE_CM98
euProtectedAreaCode.UKENNE_CM99 RIVER TORNE Quick edit Valid - stable 2025-01-29 UKENNE_CM99
euProtectedAreaCode.UKENNW_CM1 BASSENTHWAITE LAKE Quick edit Valid - stable 2025-01-29 UKENNW_CM1
euProtectedAreaCode.UKENNW_CM115SFW MORECAMBE BAY SFW CATCHMENT Quick edit Deprecated 2025-01-29 UKENNW_CM115SFW
euProtectedAreaCode.UKENNW_CM142 GLAZE BROOK Quick edit Valid - stable 2025-01-29 UKENNW_CM142
euProtectedAreaCode.UKENNW_CM143 RIVER DANE Quick edit Valid - stable 2025-01-29 UKENNW_CM143
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?