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,761 to 136,780.First6,8356,8366,8376,8386,8396,8406,8416,842Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UK14150 ST LEONARDS Quick edit Valid - stable 2025-01-29 UK14150
euProtectedAreaCode.UK14200 BEXHILL Quick edit Valid - stable 2025-01-29 UK14200
euProtectedAreaCode.UK14300 NORMAN S BAY Quick edit Valid - stable 2025-01-29 UK14300
euProtectedAreaCode.UK14400 PEVENSEY BAY Quick edit Valid - stable 2025-01-29 UK14400
euProtectedAreaCode.UK14500 EASTBOURNE Quick edit Valid - stable 2025-01-29 UK14500
euProtectedAreaCode.UK14550 BIRLING GAP Quick edit Valid - stable 2025-01-29 UK14550
euProtectedAreaCode.UK14600 SEAFORD Quick edit Valid - stable 2025-01-29 UK14600
euProtectedAreaCode.UK14700 NEWHAVEN Quick edit Deprecated - retired 2025-01-29 UK14700
euProtectedAreaCode.UK14800 SALTDEAN Quick edit Valid - stable 2025-01-29 UK14800
euProtectedAreaCode.UK14900 BRIGHTON KEMPTOWN Quick edit Valid - stable 2025-01-29 UK14900
euProtectedAreaCode.UK14950 BRIGHTON CENTRAL Quick edit Valid - stable 2025-01-29 UK14950
euProtectedAreaCode.UK15000 HOVE Quick edit Valid - stable 2025-01-29 UK15000
euProtectedAreaCode.UK15100 SOUTHWICK Quick edit Valid - stable 2025-01-29 UK15100
euProtectedAreaCode.UK15200 SHOREHAM BEACH Quick edit Valid - stable 2025-01-29 UK15200
euProtectedAreaCode.UK15300 LANCING BEACH GREEN Quick edit Valid - stable 2025-01-29 UK15300
euProtectedAreaCode.UK15400 WORTHING Quick edit Valid - stable 2025-01-29 UK15400
euProtectedAreaCode.UK15500 LITTLEHAMPTON Quick edit Valid - stable 2025-01-29 UK15500
euProtectedAreaCode.UK15600 MIDDLETON-ON-SEA Quick edit Valid - stable 2025-01-29 UK15600
euProtectedAreaCode.UK15650 FELPHAM Quick edit Valid - stable 2025-01-29 UK15650
euProtectedAreaCode.UK15680 BOGNOR REGIS EAST Quick edit Valid - stable 2025-01-29 UK15680
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?