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,901 to 137,920.First6,8926,8936,8946,8956,8966,8976,8986,899Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKS7616012_UWWTD CRUDEN BAY Quick edit Valid - experimental 2025-01-29 UKS7616012_UWWTD
euProtectedAreaCode.UKS7616013 CULLEN BAY Quick edit Valid - stable 2025-01-29 UKS7616013
euProtectedAreaCode.UKS7616014 MILLPORT BAY Quick edit Valid - stable 2025-01-29 UKS7616014
euProtectedAreaCode.UKS7616015 DORES Quick edit Valid - stable 2025-01-29 UKS7616015
euProtectedAreaCode.UKS7616016 DORNOCH Quick edit Valid - stable 2025-01-29 UKS7616016
euProtectedAreaCode.UKS7616017 DUNBAR BELHAVEN Quick edit Valid - stable 2025-01-29 UKS7616017
euProtectedAreaCode.UKS7616017_SA DUNBAR BELHAVEN Quick edit Deprecated 2025-01-29 UKS7616017_SA
euProtectedAreaCode.UKS7616017_UWWTD DUNBAR BELHAVEN Quick edit Valid - experimental 2025-01-29 UKS7616017_UWWTD
euProtectedAreaCode.UKS7616018 DUNBAR EAST Quick edit Valid - stable 2025-01-29 UKS7616018
euProtectedAreaCode.UKS7616018_SA DUNBAR EAST Quick edit Deprecated 2025-01-29 UKS7616018_SA
euProtectedAreaCode.UKS7616018_UWWTD DUNBAR EAST Quick edit Valid - experimental 2025-01-29 UKS7616018_UWWTD
euProtectedAreaCode.UKS7616019 DUNNET Quick edit Valid - stable 2025-01-29 UKS7616019
euProtectedAreaCode.UKS7616019_SA DUNNET Quick edit Deprecated 2025-01-29 UKS7616019_SA
euProtectedAreaCode.UKS7616019_UWWTD DUNNET Quick edit Valid - experimental 2025-01-29 UKS7616019_UWWTD
euProtectedAreaCode.UKS761601_SA ABERDEEN Quick edit Deprecated 2025-01-29 UKS761601_SA
euProtectedAreaCode.UKS761601_UWWTD ABERDEEN Quick edit Valid - experimental 2025-01-29 UKS761601_UWWTD
euProtectedAreaCode.UKS761602 ABERDOUR SILVERSANDS Quick edit Valid - stable 2025-01-29 UKS761602
euProtectedAreaCode.UKS7616021 ETTRICK BAY Quick edit Valid - stable 2025-01-29 UKS7616021
euProtectedAreaCode.UKS7616022 EYEMOUTH Quick edit Valid - stable 2025-01-29 UKS7616022
euProtectedAreaCode.UKS7616023 FRASERBURGH TIGER HILL Quick edit Valid - stable 2025-01-29 UKS7616023
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?