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 138,021 to 138,040.First6,8986,8996,9006,9016,9026,9036,9046,905Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKS7616088 MONIFIETH Quick edit Valid - stable 2025-01-29 UKS7616088
euProtectedAreaCode.UKS7616089 FISHERROW SANDS Quick edit Deprecated - retired 2025-01-29 UKS7616089
euProtectedAreaCode.UKS761609 CARNOUSTIE Quick edit Valid - stable 2025-01-29 UKS761609
euProtectedAreaCode.UKS7616090 COLLIESTON Quick edit Valid - stable 2025-01-29 UKS7616090
euProtectedAreaCode.UKS7616091 SAND BEACH Quick edit Valid - stable 2025-01-29 UKS7616091
euProtectedAreaCode.UKS7616092 GAIRLOCH BEACH Quick edit Valid - stable 2025-01-29 UKS7616092
euProtectedAreaCode.UKS7616093 CRUDEN BAY Quick edit Valid - stable 2025-01-29 UKS7616093
euProtectedAreaCode.UKS79923113 DORNOCH FIRTH Quick edit Deprecated 2025-01-29 UKS79923113
euProtectedAreaCode.UKS7992312 LOCH ETIVE Quick edit Deprecated 2025-01-29 UKS7992312
euProtectedAreaCode.UKS7992317 CROMARTY BAY Quick edit Deprecated 2025-01-29 UKS7992317
euProtectedAreaCode.UKS7992328 LOCH KISHORN NORTH WEST Quick edit Deprecated 2025-01-29 UKS7992328
euProtectedAreaCode.UKSW1 HOLY ISLAND Quick edit Valid - stable 2025-01-29 UKSW1
euProtectedAreaCode.UKSW10 WALTON BACKWATERS Quick edit Valid - stable 2025-01-29 UKSW10
euProtectedAreaCode.UKSW108 DEE EAST Quick edit Valid - stable 2025-01-29 UKSW108
euProtectedAreaCode.UKSW109 NORTH WIRRAL EAST Quick edit Valid - stable 2025-01-29 UKSW109
euProtectedAreaCode.UKSW11 OSEA ISLAND Quick edit Valid - stable 2025-01-29 UKSW11
euProtectedAreaCode.UKSW110 NORTH WIRRAL WEST Quick edit Valid - stable 2025-01-29 UKSW110
euProtectedAreaCode.UKSW111 RIBBLE Quick edit Valid - stable 2025-01-29 UKSW111
euProtectedAreaCode.UKSW113 LUNE WYRE ESTUARY Quick edit Valid - stable 2025-01-29 UKSW113
euProtectedAreaCode.UKSW114 LUNE BROADFLEET AND PLOVER SCAR M Quick edit Valid - stable 2025-01-29 UKSW114
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?