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,781 to 136,800.First6,8366,8376,8386,8396,8406,8416,8426,843Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UK15700 BOGNOR REGIS ALDWICK Quick edit Valid - stable 2025-01-29 UK15700
euProtectedAreaCode.UK15800 PAGHAM Quick edit Valid - stable 2025-01-29 UK15800
euProtectedAreaCode.UK15900 SELSEY Quick edit Valid - stable 2025-01-29 UK15900
euProtectedAreaCode.UK16000 BRACKLESHAM BAY Quick edit Valid - stable 2025-01-29 UK16000
euProtectedAreaCode.UK16100 WEST WITTERING Quick edit Valid - stable 2025-01-29 UK16100
euProtectedAreaCode.UK16300 EASTOKE Quick edit Valid - stable 2025-01-29 UK16300
euProtectedAreaCode.UK16350 BEACHLANDS CENTRAL Quick edit Valid - stable 2025-01-29 UK16350
euProtectedAreaCode.UK16400 BEACHLANDS WEST Quick edit Valid - stable 2025-01-29 UK16400
euProtectedAreaCode.UK16500 EASTNEY Quick edit Valid - stable 2025-01-29 UK16500
euProtectedAreaCode.UK16600 SOUTHSEA EAST Quick edit Valid - stable 2025-01-29 UK16600
euProtectedAreaCode.UK16700 STOKES BAY Quick edit Valid - stable 2025-01-29 UK16700
euProtectedAreaCode.UK16800 LEE-ON-SOLENT Quick edit Valid - stable 2025-01-29 UK16800
euProtectedAreaCode.UK16850 HILLHEAD Quick edit Valid - stable 2025-01-29 UK16850
euProtectedAreaCode.UK16900 CALSHOT Quick edit Valid - stable 2025-01-29 UK16900
euProtectedAreaCode.UK17000 LEPE Quick edit Valid - stable 2025-01-29 UK17000
euProtectedAreaCode.UK17100 MILFORD-ON-SEA Quick edit Valid - stable 2025-01-29 UK17100
euProtectedAreaCode.UK17200 CHRISTCHURCH BAY Quick edit Valid - stable 2025-01-29 UK17200
euProtectedAreaCode.UK17300 HIGHCLIFFE Quick edit Valid - stable 2025-01-29 UK17300
euProtectedAreaCode.UK17400 COMPTON BAY Quick edit Valid - stable 2025-01-29 UK17400
euProtectedAreaCode.UK17500 TOTLAND BAY Quick edit Valid - stable 2025-01-29 UK17500
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?