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 136,861 to 136,880.First6,8406,8416,8426,8436,8446,8456,8466,847Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UK22500 DAWLISH TOWN Quick edit Valid - stable 2025-01-29 UK22500
euProtectedAreaCode.UK22600 DAWLISH CORYTON COVE Quick edit Valid - stable 2025-01-29 UK22600
euProtectedAreaCode.UK22700 TEIGNMOUTH HOLCOMBE Quick edit Valid - stable 2025-01-29 UK22700
euProtectedAreaCode.UK22800 TEIGNMOUTH TOWN Quick edit Valid - stable 2025-01-29 UK22800
euProtectedAreaCode.UK22900 SHALDON Quick edit Valid - stable 2025-01-29 UK22900
euProtectedAreaCode.UK23000 NESS COVE Quick edit Valid - stable 2025-01-29 UK23000
euProtectedAreaCode.UK23100 MAIDENCOMBE Quick edit Valid - stable 2025-01-29 UK23100
euProtectedAreaCode.UK23200 WATCOMBE Quick edit Valid - stable 2025-01-29 UK23200
euProtectedAreaCode.UK23300 ODDICOMBE Quick edit Valid - stable 2025-01-29 UK23300
euProtectedAreaCode.UK23400 BABBACOMBE Quick edit Valid - stable 2025-01-29 UK23400
euProtectedAreaCode.UK23501 ANSTEYS COVE TORQUAY Quick edit Valid - stable 2025-01-29 UK23501
euProtectedAreaCode.UK23600 MEADFOOT Quick edit Valid - stable 2025-01-29 UK23600
euProtectedAreaCode.UK23700 BEACON COVE Quick edit Valid - stable 2025-01-29 UK23700
euProtectedAreaCode.UK23800 TORRE ABBEY Quick edit Valid - stable 2025-01-29 UK23800
euProtectedAreaCode.UK23900 HOLLICOMBE Quick edit Valid - stable 2025-01-29 UK23900
euProtectedAreaCode.UK24000 PAIGNTON PRESTON SANDS Quick edit Valid - stable 2025-01-29 UK24000
euProtectedAreaCode.UK24100 PAIGNTON PAIGNTON SANDS Quick edit Valid - stable 2025-01-29 UK24100
euProtectedAreaCode.UK24200 GOODRINGTON Quick edit Valid - stable 2025-01-29 UK24200
euProtectedAreaCode.UK24300 BROADSANDS Quick edit Valid - stable 2025-01-29 UK24300
euProtectedAreaCode.UK24500 BREAKWATER BEACH SHOALSTONE Quick edit Valid - stable 2025-01-29 UK24500
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?