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,201 to 137,220.First6,8576,8586,8596,8606,8616,8626,8636,864Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKCMSC9127136 RIVER ESK Quick edit Valid - stable 2025-01-29 UKCMSC9127136
euProtectedAreaCode.UKCMSC9127137 POW BURN AYRSHIRE Quick edit Valid - stable 2025-01-29 UKCMSC9127137
euProtectedAreaCode.UKCMSC9127138 RIVER AVON Quick edit Valid - stable 2025-01-29 UKCMSC9127138
euProtectedAreaCode.UKCMSC9127139 RIVER URR Quick edit Valid - stable 2025-01-29 UKCMSC9127139
euProtectedAreaCode.UKCMSC912714 LOCH MAHAICK Quick edit Valid - stable 2025-01-29 UKCMSC912714
euProtectedAreaCode.UKCMSC9127140 EAST POW BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127140
euProtectedAreaCode.UKCMSC9127141 TARFF WATER Quick edit Valid - stable 2025-01-29 UKCMSC9127141
euProtectedAreaCode.UKCMSC9127142 RIVER KELVIN Quick edit Valid - stable 2025-01-29 UKCMSC9127142
euProtectedAreaCode.UKCMSC9127143 MURKLE BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127143
euProtectedAreaCode.UKCMSC9127144 LUGTON WATER Quick edit Valid - stable 2025-01-29 UKCMSC9127144
euProtectedAreaCode.UKCMSC9127145 BLACK CART WATER Quick edit Valid - stable 2025-01-29 UKCMSC9127145
euProtectedAreaCode.UKCMSC9127146 RIVER CLYDE Quick edit Valid - stable 2025-01-29 UKCMSC9127146
euProtectedAreaCode.UKCMSC9127147 BLACK DEVON Quick edit Valid - stable 2025-01-29 UKCMSC9127147
euProtectedAreaCode.UKCMSC9127148 MACHRIHANISH WATER Quick edit Valid - stable 2025-01-29 UKCMSC9127148
euProtectedAreaCode.UKCMSC9127149 ACHAIRN BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127149
euProtectedAreaCode.UKCMSC9127150 GRANGE BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127150
euProtectedAreaCode.UKCMSC9127151 WEST PEFFER BURN MILL BURN NORTH Quick edit Valid - stable 2025-01-29 UKCMSC9127151
euProtectedAreaCode.UKCMSC9127152 RIVER IRVINE Quick edit Valid - stable 2025-01-29 UKCMSC9127152
euProtectedAreaCode.UKCMSC9127153 EYE WATER Quick edit Valid - stable 2025-01-29 UKCMSC9127153
euProtectedAreaCode.UKCMSC9127154 BOYNE BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127154
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?