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,141 to 137,160.First6,8546,8556,8566,8576,8586,8596,8606,861Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UK44400 WALNEY WEST SHORE Quick edit Valid - stable 2025-01-29 UK44400
euProtectedAreaCode.UK44500 ROAN HEAD Quick edit Deprecated - retired 2025-01-29 UK44500
euProtectedAreaCode.UK44590 ASKAM-IN-FURNESS Quick edit Deprecated - retired 2025-01-29 UK44590
euProtectedAreaCode.UK44800 HAVERIGG Quick edit Valid - stable 2025-01-29 UK44800
euProtectedAreaCode.UK45200 SILECROFT Quick edit Valid - stable 2025-01-29 UK45200
euProtectedAreaCode.UK45600 SEASCALE Quick edit Valid - stable 2025-01-29 UK45600
euProtectedAreaCode.UK45625 WINDERMERE LAKESIDE YMCA Quick edit Valid - stable 2025-01-29 UK45625
euProtectedAreaCode.UK45650 WINDERMERE MILLERGROUND LANDING Quick edit Valid - stable 2025-01-29 UK45650
euProtectedAreaCode.UK45675 WINDERMERE RAYRIGG MEADOW Quick edit Valid - stable 2025-01-29 UK45675
euProtectedAreaCode.UK45700 WINDERMERE FELLFOOT Quick edit Valid - stable 2025-01-29 UK45700
euProtectedAreaCode.UK45920 ST BEES Quick edit Valid - stable 2025-01-29 UK45920
euProtectedAreaCode.UK46000 ALLONBY SOUTH Quick edit Deprecated - retired 2025-01-29 UK46000
euProtectedAreaCode.UK46100 ALLONBY Quick edit Valid - stable 2025-01-29 UK46100
euProtectedAreaCode.UK46300 SILLOTH Quick edit Deprecated - retired 2025-01-29 UK46300
euProtectedAreaCode.UK46500 SKINBURNESS Quick edit Deprecated - retired 2025-01-29 UK46500
euProtectedAreaCode.UKCASSWPA11 CROMARTY BAY Quick edit Valid - stable 2025-01-29 UKCASSWPA11
euProtectedAreaCode.UKCASSWPA13 DORNOCH FIRTH Quick edit Valid - stable 2025-01-29 UKCASSWPA13
euProtectedAreaCode.UKCASSWPA37 LOCH ETIVE Quick edit Valid - stable 2025-01-29 UKCASSWPA37
euProtectedAreaCode.UKCASSWPA44 LOCH KISHORN Quick edit Valid - stable 2025-01-29 UKCASSWPA44
euProtectedAreaCode.UKCMSC912711 LAKE OF MENTEITH Quick edit Valid - stable 2025-01-29 UKCMSC912711
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?