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,981 to 137,000.First6,8466,8476,8486,8496,8506,8516,8526,853Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UK33100 ROCK Quick edit Deprecated - retired 2025-01-29 UK33100
euProtectedAreaCode.UK33200 DAYMER BAY Quick edit Valid - stable 2025-01-29 UK33200
euProtectedAreaCode.UK33300 POLZEATH Quick edit Valid - stable 2025-01-29 UK33300
euProtectedAreaCode.UK33350 TREBARWITH STRAND Quick edit Valid - stable 2025-01-29 UK33350
euProtectedAreaCode.UK33360 CRACKINGTON HAVEN Quick edit Valid - stable 2025-01-29 UK33360
euProtectedAreaCode.UK33400 WIDEMOUTH SAND Quick edit Valid - stable 2025-01-29 UK33400
euProtectedAreaCode.UK33500 SUMMERLEAZE Quick edit Valid - stable 2025-01-29 UK33500
euProtectedAreaCode.UK33600 CROOKLETS Quick edit Valid - stable 2025-01-29 UK33600
euProtectedAreaCode.UK33650 NORTHCOTT MOUTH Quick edit Valid - stable 2025-01-29 UK33650
euProtectedAreaCode.UK33700 SANDYMOUTH Quick edit Valid - stable 2025-01-29 UK33700
euProtectedAreaCode.UK33800 HARTLAND QUAY Quick edit Valid - stable 2025-01-29 UK33800
euProtectedAreaCode.UK33900 WESTWARD HO Quick edit Valid - stable 2025-01-29 UK33900
euProtectedAreaCode.UK34000 INSTOW Quick edit Deprecated - retired 2025-01-29 UK34000
euProtectedAreaCode.UK34100 SAUNTON SANDS Quick edit Valid - stable 2025-01-29 UK34100
euProtectedAreaCode.UK34200 CROYDE BAY Quick edit Valid - stable 2025-01-29 UK34200
euProtectedAreaCode.UK34300 PUTSBOROUGH Quick edit Valid - stable 2025-01-29 UK34300
euProtectedAreaCode.UK34400 WOOLACOMBE VILLAGE Quick edit Valid - stable 2025-01-29 UK34400
euProtectedAreaCode.UK34410 COMBESGATE BEACH WOOLACOMBE Quick edit Valid - stable 2025-01-29 UK34410
euProtectedAreaCode.UK34450 ILFRACOMBE TUNNELS BEACH Quick edit Valid - stable 2025-01-29 UK34450
euProtectedAreaCode.UK34500 ILFRACOMBE WILDERSMOUTH Quick edit Deprecated - retired 2025-01-29 UK34500
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?