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 1 to 20.FirstPrev12345678Last
Id Label Status Status Modified Notation
euProtectedAreaCode.AL101 VELIPOJA Quick edit Valid - stable 2022-08-11 AL101
euProtectedAreaCode.AL102 VELIPOJA Quick edit Valid - stable 2022-08-11 AL102
euProtectedAreaCode.AL103 VELIPOJA Quick edit Valid - stable 2022-08-11 AL103
euProtectedAreaCode.AL104 VELIPOJA Quick edit Valid - stable 2022-08-11 AL104
euProtectedAreaCode.AL105 VELIPOJA Quick edit Valid - stable 2022-08-11 AL105
euProtectedAreaCode.AL106 VELIPOJA Quick edit Valid - stable 2022-08-11 AL106
euProtectedAreaCode.AL107 VELIPOJA Quick edit Valid - stable 2022-08-11 AL107
euProtectedAreaCode.AL108 LIN Quick edit Valid - stable 2022-08-11 AL108
euProtectedAreaCode.AL109 LIN Quick edit Valid - stable 2022-08-11 AL109
euProtectedAreaCode.AL110 POGRADEC Quick edit Valid - stable 2022-08-11 AL110
euProtectedAreaCode.AL111 POGRADEC Quick edit Valid - stable 2022-08-11 AL111
euProtectedAreaCode.AL112 POGRADEC Quick edit Valid - stable 2022-08-11 AL112
euProtectedAreaCode.AL113 TUSHEMISHT Quick edit Valid - stable 2022-08-11 AL113
euProtectedAreaCode.AL114 POGRADEC Quick edit Valid - stable 2022-08-11 AL114
euProtectedAreaCode.AL115 POGRADEC Quick edit Valid - stable 2022-08-11 AL115
euProtectedAreaCode.AL201 SHENGJIN Quick edit Valid - stable 2022-08-11 AL201
euProtectedAreaCode.AL202 SHENGJIN Quick edit Valid - stable 2022-08-11 AL202
euProtectedAreaCode.AL203 SHENGJIN Quick edit Valid - stable 2022-08-11 AL203
euProtectedAreaCode.AL204 SHENGJIN Quick edit Valid - stable 2022-08-11 AL204
euProtectedAreaCode.AL205 SHENGJIN Quick edit Valid - stable 2022-08-11 AL205
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?