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,741 to 136,760.First6,8346,8356,8366,8376,8386,8396,8406,841Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UK12600 MARGATE FULSAM ROCK Quick edit Valid - stable 2025-01-29 UK12600
euProtectedAreaCode.UK12630 WALPOLE BAY MARGATE Quick edit Valid - stable 2025-01-29 UK12630
euProtectedAreaCode.UK12660 BOTANY BAY BROADSTAIRS Quick edit Valid - stable 2025-01-29 UK12660
euProtectedAreaCode.UK12700 JOSS BAY BROADSTAIRS Quick edit Valid - stable 2025-01-29 UK12700
euProtectedAreaCode.UK12750 BROADSTAIRS STONE BAY Quick edit Valid - stable 2025-01-29 UK12750
euProtectedAreaCode.UK12800 BROADSTAIRS VIKING BAY Quick edit Valid - stable 2025-01-29 UK12800
euProtectedAreaCode.UK12850 RAMSGATE SANDS Quick edit Valid - stable 2025-01-29 UK12850
euProtectedAreaCode.UK12900 RAMSGATE WESTERN UNDERCLIFFE Quick edit Valid - stable 2025-01-29 UK12900
euProtectedAreaCode.UK13000 SANDWICH BAY Quick edit Valid - stable 2025-01-29 UK13000
euProtectedAreaCode.UK13100 DEAL CASTLE Quick edit Valid - stable 2025-01-29 UK13100
euProtectedAreaCode.UK13200 ST MARGARET S BAY Quick edit Valid - stable 2025-01-29 UK13200
euProtectedAreaCode.UK13300 FOLKESTONE Quick edit Valid - stable 2025-01-29 UK13300
euProtectedAreaCode.UK13400 SANDGATE Quick edit Valid - stable 2025-01-29 UK13400
euProtectedAreaCode.UK13500 HYTHE Quick edit Valid - stable 2025-01-29 UK13500
euProtectedAreaCode.UK13600 DYMCHURCH Quick edit Valid - stable 2025-01-29 UK13600
euProtectedAreaCode.UK13700 ST MARYS BAY KENT Quick edit Valid - stable 2025-01-29 UK13700
euProtectedAreaCode.UK13800 LITTLESTONE Quick edit Valid - stable 2025-01-29 UK13800
euProtectedAreaCode.UK13900 CAMBER Quick edit Valid - stable 2025-01-29 UK13900
euProtectedAreaCode.UK14000 WINCHELSEA Quick edit Valid - stable 2025-01-29 UK14000
euProtectedAreaCode.UK14100 HASTINGS PELHAM BEACH Quick edit Valid - stable 2025-01-29 UK14100
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?