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,221 to 137,240.First6,8586,8596,8606,8616,8626,8636,8646,865Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKCMSC9127155 LOCH MORE Quick edit Valid - stable 2025-01-29 UKCMSC9127155
euProtectedAreaCode.UKCMSC9127156 BURRELTON BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127156
euProtectedAreaCode.UKCMSC9127157 RIVER CARRON Quick edit Valid - stable 2025-01-29 UKCMSC9127157
euProtectedAreaCode.UKCMSC9127158 KINNESS BURN ST ANDREWS EAST SANDS BATHING WATER Quick edit Valid - stable 2025-01-29 UKCMSC9127158
euProtectedAreaCode.UKCMSC9127159 RIVER DEVERON Quick edit Valid - stable 2025-01-29 UKCMSC9127159
euProtectedAreaCode.UKCMSC912716 EAST PEFFER BURN Quick edit Valid - stable 2025-01-29 UKCMSC912716
euProtectedAreaCode.UKCMSC9127160 PILTANTON BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127160
euProtectedAreaCode.UKCMSC9127161 MOCHRUM LOCH Quick edit Valid - stable 2025-01-29 UKCMSC9127161
euProtectedAreaCode.UKCMSC9127162 MOTRAY WATER Quick edit Valid - stable 2025-01-29 UKCMSC9127162
euProtectedAreaCode.UKCMSC9127163 GAIRNEY BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127163
euProtectedAreaCode.UKCMSC9127165 KIRTLE WATER Quick edit Valid - stable 2025-01-29 UKCMSC9127165
euProtectedAreaCode.UKCMSC9127166 BUDDON BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127166
euProtectedAreaCode.UKCMSC9127167 LOCHTY BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127167
euProtectedAreaCode.UKCMSC9127168 CERES BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127168
euProtectedAreaCode.UKCMSC9127169 RIVER UGIE Quick edit Valid - stable 2025-01-29 UKCMSC9127169
euProtectedAreaCode.UKCMSC912717 LOCH FITTY Quick edit Valid - stable 2025-01-29 UKCMSC912717
euProtectedAreaCode.UKCMSC9127171 FORDYCE BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127171
euProtectedAreaCode.UKCMSC9127172 SOUTH MUNDURNO BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127172
euProtectedAreaCode.UKCMSC9127173 RIVER SOUTH ESK Quick edit Valid - stable 2025-01-29 UKCMSC9127173
euProtectedAreaCode.UKCMSC9127174 MONIKIE BURN Quick edit Valid - stable 2025-01-29 UKCMSC9127174
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?