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
29 Oct 2015
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

106,312 concepts found, displaying 105,521 to 105,540.First5,2735,2745,2755,2765,2775,2785,2795,280Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKENRI74B RIVER STOUR STOUR BROOK Quick edit Valid - stable 2022-08-11 UKENRI74B
euProtectedAreaCode.UKENRI75 RIVER IVEL Quick edit Valid - stable 2022-08-11 UKENRI75
euProtectedAreaCode.UKENRI76 RIVER WISKE Quick edit Valid - stable 2022-08-11 UKENRI76
euProtectedAreaCode.UKENRI77 RIVER AVON BRISTOL Quick edit Valid - stable 2022-08-11 UKENRI77
euProtectedAreaCode.UKENRI78 RIVER AVON HAMPSHIRE Quick edit Valid - stable 2022-08-11 UKENRI78
euProtectedAreaCode.UKENRI79 RIVER WEAR Quick edit Valid - stable 2022-08-11 UKENRI79
euProtectedAreaCode.UKENRI8 RIVER BLYTHE Quick edit Valid - stable 2022-08-11 UKENRI8
euProtectedAreaCode.UKENRI80 RIVER SKERNE TEES CATCHMENT Quick edit Valid - stable 2022-08-11 UKENRI80
euProtectedAreaCode.UKENRI84B RIVER CHELMER B Quick edit Valid - stable 2022-08-11 UKENRI84B
euProtectedAreaCode.UKENRI85 RIVER WISSEY Quick edit Valid - stable 2022-08-11 UKENRI85
euProtectedAreaCode.UKENRI87 RIVER LEAM Quick edit Valid - stable 2022-08-11 UKENRI87
euProtectedAreaCode.UKENRI88 BOURNE EAU RIVER GLEN Quick edit Valid - stable 2022-08-11 UKENRI88
euProtectedAreaCode.UKENRI89 RIVER TIFFEY YARE Quick edit Valid - stable 2022-08-11 UKENRI89
euProtectedAreaCode.UKENRI9 RIVER ARROW Quick edit Valid - stable 2022-08-11 UKENRI9
euProtectedAreaCode.UKENRI90 OLD WEST ELY OUSE Quick edit Valid - stable 2022-08-11 UKENRI90
euProtectedAreaCode.UKENRI91 RIVER CAM CAMBRIDGESHIRE Quick edit Valid - stable 2022-08-11 UKENRI91
euProtectedAreaCode.UKENRI92 RIVER KENT Quick edit Valid - stable 2022-08-11 UKENRI92
euProtectedAreaCode.UKENRI93 RIVER CALDER Quick edit Valid - stable 2022-08-11 UKENRI93
euProtectedAreaCode.UKENRI94 RIVER IRWELL Quick edit Valid - stable 2022-08-11 UKENRI94
euProtectedAreaCode.UKENRI95 RIVER ALT Quick edit Valid - stable 2022-08-11 UKENRI95
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?