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,981 to 138,000.First6,8966,8976,8986,8996,9006,9016,9026,903Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKS7616056_UWWTD ST ANDREWS EAST SANDS Quick edit Valid - experimental 2025-01-29 UKS7616056_UWWTD
euProtectedAreaCode.UKS7616057 ST ANDREWS WEST SANDS Quick edit Valid - stable 2025-01-29 UKS7616057
euProtectedAreaCode.UKS7616057_SA ST ANDREWS WEST SANDS Quick edit Deprecated 2025-01-29 UKS7616057_SA
euProtectedAreaCode.UKS7616057_UWWTD ST ANDREWS WEST SANDS Quick edit Valid - experimental 2025-01-29 UKS7616057_UWWTD
euProtectedAreaCode.UKS7616058 STONEHAVEN Quick edit Valid - stable 2025-01-29 UKS7616058
euProtectedAreaCode.UKS7616059 THORNTONLOCH Quick edit Valid - stable 2025-01-29 UKS7616059
euProtectedAreaCode.UKS761606 BRIGHOUSE BAY Quick edit Valid - stable 2025-01-29 UKS761606
euProtectedAreaCode.UKS7616060 TROON SOUTH BEACH Quick edit Valid - stable 2025-01-29 UKS7616060
euProtectedAreaCode.UKS7616062 WHITESANDS Quick edit Valid - stable 2025-01-29 UKS7616062
euProtectedAreaCode.UKS7616063 YELLOW CRAIG Quick edit Valid - stable 2025-01-29 UKS7616063
euProtectedAreaCode.UKS7616064 ELIE HARBOUR AND EARLSFERRY Quick edit Valid - stable 2025-01-29 UKS7616064
euProtectedAreaCode.UKS7616065 ELIE RUBY BAY Quick edit Valid - stable 2025-01-29 UKS7616065
euProtectedAreaCode.UKS7616066 ACHMELVICH Quick edit Valid - stable 2025-01-29 UKS7616066
euProtectedAreaCode.UKS7616067 BROAD SANDS Quick edit Valid - stable 2025-01-29 UKS7616067
euProtectedAreaCode.UKS7616068 CULZEAN Quick edit Valid - stable 2025-01-29 UKS7616068
euProtectedAreaCode.UKS7616069 DHOON BAY Quick edit Valid - stable 2025-01-29 UKS7616069
euProtectedAreaCode.UKS761607 BROUGHTY FERRY Quick edit Valid - stable 2025-01-29 UKS761607
euProtectedAreaCode.UKS7616070 FINDHORN Quick edit Valid - stable 2025-01-29 UKS7616070
euProtectedAreaCode.UKS7616071 HEADS OF AYR Quick edit Valid - stable 2025-01-29 UKS7616071
euProtectedAreaCode.UKS7616072 KINGHORN HARBOUR BEACH Quick edit Valid - stable 2025-01-29 UKS7616072
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?