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,861 to 137,880.First6,8906,8916,8926,8936,8946,8956,8966,897Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKRISC9127168 RIVER YTHAN - METHLICK TO ELLON Quick edit Valid - stable 2025-01-29 UKRISC9127168
euProtectedAreaCode.UKRISC9127169 YOULIE BURN BRONIE BURN Quick edit Valid - stable 2025-01-29 UKRISC9127169
euProtectedAreaCode.UKRISC912717 MURKLE BURN Quick edit Valid - stable 2025-01-29 UKRISC912717
euProtectedAreaCode.UKRISC9127170 GAIRIE BURN Quick edit Valid - stable 2025-01-29 UKRISC9127170
euProtectedAreaCode.UKRISC9127171 GLAMIS BURN Quick edit Valid - stable 2025-01-29 UKRISC9127171
euProtectedAreaCode.UKRISC9127172 MEIGLE BURN Quick edit Valid - stable 2025-01-29 UKRISC9127172
euProtectedAreaCode.UKRISC9127173 RIVER DOON D S MUCK WATER Quick edit Valid - stable 2025-01-29 UKRISC9127173
euProtectedAreaCode.UKRISC9127174 RIVER KELVIN GLAZERT WATER TO TIDAL LIMIT Quick edit Valid - stable 2025-01-29 UKRISC9127174
euProtectedAreaCode.UKRISC9127175 LUGGIE WATER KELVIN TO MOLLINS BURN Quick edit Valid - stable 2025-01-29 UKRISC9127175
euProtectedAreaCode.UKRISC9127176 LUGGIE WATER U S MOLLINS BURN Quick edit Valid - stable 2025-01-29 UKRISC9127176
euProtectedAreaCode.UKRISC9127177 BOTHLIN BURN GARNKIRK BURN TO LUGGIE CONFLUENCE Quick edit Valid - stable 2025-01-29 UKRISC9127177
euProtectedAreaCode.UKRISC9127178 RIVER ALMOND SOURCE TO FOULSHIELS BURN CONFLUENCE Quick edit Valid - stable 2025-01-29 UKRISC9127178
euProtectedAreaCode.UKRISC9127179 KINNESS BURN INCLUDING CAIRNSMILL BURN Quick edit Valid - stable 2025-01-29 UKRISC9127179
euProtectedAreaCode.UKRISC912718 RIVER NORTH ESK CONFLUENCE WITH CRUICK WATER TO ESTUARY Quick edit Valid - stable 2025-01-29 UKRISC912718
euProtectedAreaCode.UKRISC9127180 NIDDRY BURN Quick edit Valid - stable 2025-01-29 UKRISC9127180
euProtectedAreaCode.UKRISC9127181 GOGAR BURN SOURCE TO UNION CANAL Quick edit Valid - stable 2025-01-29 UKRISC9127181
euProtectedAreaCode.UKRISC9127182 BROX BURN RYAL BURN CONFLUENCE TO RIVER ALMOND Quick edit Valid - stable 2025-01-29 UKRISC9127182
euProtectedAreaCode.UKRISC9127183 RIVER CARRON BONNY WATER CONFLUENCE TO CARRON ESTUARY Quick edit Valid - stable 2025-01-29 UKRISC9127183
euProtectedAreaCode.UKRISC9127184 BONNY WATER RED BURN Quick edit Valid - stable 2025-01-29 UKRISC9127184
euProtectedAreaCode.UKRISC9127185 PENNYLAND BURN MEIN WATER Quick edit Valid - stable 2025-01-29 UKRISC9127185
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?