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,641 to 137,660.First6,8796,8806,8816,8826,8836,8846,8856,886Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKGBNIPA3_20026 PORTRUSH CURRAN STRAND Quick edit Valid - stable 2025-01-29 UKGBNIPA3_20026
euProtectedAreaCode.UKGBNIPA3_20027 PORTRUSH WHITEROCKS Quick edit Valid - stable 2025-01-29 UKGBNIPA3_20027
euProtectedAreaCode.UKGBNIPA3_20028 CLOUGHEY Quick edit Valid - stable 2025-01-29 UKGBNIPA3_20028
euProtectedAreaCode.UKGBNIPA3_20029 KILCLIEF Quick edit Valid - stable 2025-01-29 UKGBNIPA3_20029
euProtectedAreaCode.UKGBNIPA3_20030 BALLYHORNAN Quick edit Valid - stable 2025-01-29 UKGBNIPA3_20030
euProtectedAreaCode.UKGIB03 EUROPA POINT GIBRALTAR Quick edit Deprecated 2025-01-29 UKGIB03
euProtectedAreaCode.UKGIB10 EASTERN BEACH Quick edit Valid - stable 2025-01-29 UKGIB10
euProtectedAreaCode.UKGIB20 CATALAN BAY Quick edit Valid - stable 2025-01-29 UKGIB20
euProtectedAreaCode.UKGIB30 SANDY BAY Quick edit Valid - stable 2025-01-29 UKGIB30
euProtectedAreaCode.UKGIB40 LITTLE BAY Quick edit Valid - stable 2025-01-29 UKGIB40
euProtectedAreaCode.UKGIB50 CAMP BAY Quick edit Valid - stable 2025-01-29 UKGIB50
euProtectedAreaCode.UKGIB60 WESTERN BEACH Quick edit Valid - stable 2025-01-29 UKGIB60
euProtectedAreaCode.UKH1407-10700 WAVENEY Quick edit Deprecated - retired 2025-01-29 UKH1407-10700
euProtectedAreaCode.UKLKSC912711 LOCH OF ABOYNE Quick edit Valid - stable 2025-01-29 UKLKSC912711
euProtectedAreaCode.UKLKSC9127110 LOCH MAHAICK Quick edit Valid - stable 2025-01-29 UKLKSC9127110
euProtectedAreaCode.UKLKSC9127111 STRATHCLYDE LOCH Quick edit Valid - stable 2025-01-29 UKLKSC9127111
euProtectedAreaCode.UKLKSC9127112 FORFAR LOCH Quick edit Valid - stable 2025-01-29 UKLKSC9127112
euProtectedAreaCode.UKLKSC9127113 MOCHRUM LOCH Quick edit Valid - stable 2025-01-29 UKLKSC9127113
euProtectedAreaCode.UKLKSC9127114 LOCH MORE Quick edit Valid - stable 2025-01-29 UKLKSC9127114
euProtectedAreaCode.UKLKSC9127115 LOCH OF HARRAY Quick edit Valid - stable 2025-01-29 UKLKSC9127115
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?