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
29 Oct 2015
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

106,312 concepts found, displaying 105,461 to 105,480.First5,2705,2715,2725,2735,2745,2755,2765,277Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKENRI141 RIVER BRUE SHEPPEY ALHAM Quick edit Valid - stable 2022-08-11 UKENRI141
euProtectedAreaCode.UKENRI142 GLAZE BROOK Quick edit Valid - stable 2022-08-11 UKENRI142
euProtectedAreaCode.UKENRI143 RIVER DANE Quick edit Valid - stable 2022-08-11 UKENRI143
euProtectedAreaCode.UKENRI144 RIVER TAME Quick edit Valid - stable 2022-08-11 UKENRI144
euProtectedAreaCode.UKENRI145 RIVER DEVON AND CAR DYKE Quick edit Valid - stable 2022-08-11 UKENRI145
euProtectedAreaCode.UKENRI146 ADUR EAST Quick edit Valid - stable 2022-08-11 UKENRI146
euProtectedAreaCode.UKENRI147 RIVER OUSE Quick edit Valid - stable 2022-08-11 UKENRI147
euProtectedAreaCode.UKENRI148 RIVER TONE Quick edit Valid - stable 2022-08-11 UKENRI148
euProtectedAreaCode.UKENRI149 CHEDDAR-YEO Quick edit Valid - stable 2022-08-11 UKENRI149
euProtectedAreaCode.UKENRI15 RIVER WEY Quick edit Valid - stable 2022-08-11 UKENRI15
euProtectedAreaCode.UKENRI151 RIVER WYRE Quick edit Valid - stable 2022-08-11 UKENRI151
euProtectedAreaCode.UKENRI152 HYDE BROOK Quick edit Valid - stable 2022-08-11 UKENRI152
euProtectedAreaCode.UKENRI153 RIVER SOW AND RIVER PENK Quick edit Valid - stable 2022-08-11 UKENRI153
euProtectedAreaCode.UKENRI154 RIVER DARWEN Quick edit Valid - stable 2022-08-11 UKENRI154
euProtectedAreaCode.UKENRI155 RIVER WEAVER Quick edit Valid - stable 2022-08-11 UKENRI155
euProtectedAreaCode.UKENRI156 SINDERLAND BROOK Quick edit Valid - stable 2022-08-11 UKENRI156
euProtectedAreaCode.UKENRI157 RIVER WANDLE Quick edit Valid - stable 2022-08-11 UKENRI157
euProtectedAreaCode.UKENRI16 RIVER BLACKWATER HAMPSHIRE Quick edit Valid - stable 2022-08-11 UKENRI16
euProtectedAreaCode.UKENRI17 RIVER THAMES Quick edit Valid - stable 2022-08-11 UKENRI17
euProtectedAreaCode.UKENRI18 RIVER RAY WILTSHIRE Quick edit Valid - stable 2022-08-11 UKENRI18
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?