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 (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

99,985 concepts found, displaying 98,921 to 98,940.First4,9434,9444,9454,9464,9474,9484,9494,950Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKCMSC9127120 LOCH GELLY Quick edit Valid - stable 2019-11-05 UKCMSC9127120
euProtectedAreaCode.UKCMSC9127121 LUNAN WATER Quick edit Valid - stable 2019-11-05 UKCMSC9127121
euProtectedAreaCode.UKCMSC9127122 WHITE LOCH Quick edit Valid - stable 2019-11-05 UKCMSC9127122
euProtectedAreaCode.UKCMSC9127123 RIVER DOON Quick edit Valid - stable 2019-11-05 UKCMSC9127123
euProtectedAreaCode.UKCMSC9127124 SAUCHET WATER Quick edit Deprecated 2019-11-05 UKCMSC9127124
euProtectedAreaCode.UKCMSC9127125 DRONACHY BURN Quick edit Valid - stable 2019-11-05 UKCMSC9127125
euProtectedAreaCode.UKCMSC9127126 BURDIEHOUSE BURN Quick edit Valid - stable 2019-11-05 UKCMSC9127126
euProtectedAreaCode.UKCMSC9127127 UPPER CREE Quick edit Deprecated 2019-11-05 UKCMSC9127127
euProtectedAreaCode.UKCMSC9127128 PARDOVAN BURN Quick edit Valid - stable 2019-11-05 UKCMSC9127128
euProtectedAreaCode.UKCMSC9127129 BLACK WATER Quick edit Valid - stable 2019-11-05 UKCMSC9127129
euProtectedAreaCode.UKCMSC912713 DIGHTY WATER Quick edit Valid - stable 2019-11-05 UKCMSC912713
euProtectedAreaCode.UKCMSC9127130 LOCH OF HARRAY Quick edit Valid - stable 2019-11-05 UKCMSC9127130
euProtectedAreaCode.UKCMSC9127131 LYNE BURN Quick edit Valid - stable 2019-11-05 UKCMSC9127131
euProtectedAreaCode.UKCMSC9127132 DRUMMOND BURN Quick edit Valid - stable 2019-11-05 UKCMSC9127132
euProtectedAreaCode.UKCMSC9127133 MURRAY BURN Quick edit Valid - stable 2019-11-05 UKCMSC9127133
euProtectedAreaCode.UKCMSC9127135 RIVER NORTH ESK Quick edit Valid - stable 2019-11-05 UKCMSC9127135
euProtectedAreaCode.UKCMSC9127136 RIVER ESK Quick edit Valid - stable 2019-11-05 UKCMSC9127136
euProtectedAreaCode.UKCMSC9127137 POW BURN AYRSHIRE Quick edit Valid - stable 2019-11-05 UKCMSC9127137
euProtectedAreaCode.UKCMSC9127138 RIVER AVON Quick edit Valid - stable 2019-11-05 UKCMSC9127138
euProtectedAreaCode.UKCMSC9127139 RIVER URR Quick edit Valid - stable 2019-11-05 UKCMSC9127139
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?