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,381 to 137,400.First6,8666,8676,8686,8696,8706,8716,8726,873Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKENRI110 RIVER ITCHEN HAMPSHIRE Quick edit Valid - stable 2025-01-29 UKENRI110
euProtectedAreaCode.UKENRI114 BLACK SEWER Quick edit Valid - stable 2025-01-29 UKENRI114
euProtectedAreaCode.UKENRI115 UPPER BRISTOL AVON Quick edit Valid - stable 2025-01-29 UKENRI115
euProtectedAreaCode.UKENRI116 RIVER WYLYE Quick edit Valid - stable 2025-01-29 UKENRI116
euProtectedAreaCode.UKENRI118 EAST LOOE LISKEARD Quick edit Valid - stable 2025-01-29 UKENRI118
euProtectedAreaCode.UKENRI119 ST AUSTELL RIVER Quick edit Valid - stable 2025-01-29 UKENRI119
euProtectedAreaCode.UKENRI12 RIVER CREEDY Quick edit Valid - stable 2025-01-29 UKENRI12
euProtectedAreaCode.UKENRI122 RIVER HAMBLE Quick edit Valid - stable 2025-01-29 UKENRI122
euProtectedAreaCode.UKENRI126 LITTLE STOUR Quick edit Valid - stable 2025-01-29 UKENRI126
euProtectedAreaCode.UKENRI128 RIVER ROTHER WEST Quick edit Valid - stable 2025-01-29 UKENRI128
euProtectedAreaCode.UKENRI129 WALDRON GHYLL AND RIVER CUCKMERE Quick edit Valid - stable 2025-01-29 UKENRI129
euProtectedAreaCode.UKENRI13 RIVER TEST Quick edit Valid - stable 2025-01-29 UKENRI13
euProtectedAreaCode.UKENRI130 RIVER TRENT Quick edit Valid - stable 2025-01-29 UKENRI130
euProtectedAreaCode.UKENRI131 BADSEY BROOK Quick edit Valid - stable 2025-01-29 UKENRI131
euProtectedAreaCode.UKENRI132 GILWISKAW BROOK AND RIVER MEASE Quick edit Valid - stable 2025-01-29 UKENRI132
euProtectedAreaCode.UKENRI133 REA BROOK Quick edit Valid - stable 2025-01-29 UKENRI133
euProtectedAreaCode.UKENRI134 RIVER ITCHEN Quick edit Valid - stable 2025-01-29 UKENRI134
euProtectedAreaCode.UKENRI135 RIVER STRINE STRINE BROOK Quick edit Valid - stable 2025-01-29 UKENRI135
euProtectedAreaCode.UKENRI136 RIVER SWIFT OXFORD CANAL Quick edit Valid - stable 2025-01-29 UKENRI136
euProtectedAreaCode.UKENRI137 RIVER SALWARPE Quick edit Valid - stable 2025-01-29 UKENRI137
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?