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 97,941 to 97,960.First4,8944,8954,8964,8974,8984,8994,9004,901Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PLGW2000148 148 Quick edit Valid - stable 2022-08-11 PLGW2000148
euProtectedAreaCode.PLGW2000149 149 Quick edit Valid - stable 2022-08-11 PLGW2000149
euProtectedAreaCode.PLGW200015 15 Quick edit Valid - stable 2022-08-11 PLGW200015
euProtectedAreaCode.PLGW2000150 150 Quick edit Valid - stable 2022-08-11 PLGW2000150
euProtectedAreaCode.PLGW2000151 151 Quick edit Valid - stable 2022-08-11 PLGW2000151
euProtectedAreaCode.PLGW2000152 152 Quick edit Valid - stable 2022-08-11 PLGW2000152
euProtectedAreaCode.PLGW2000153 153 Quick edit Valid - stable 2022-08-11 PLGW2000153
euProtectedAreaCode.PLGW2000154 154 Quick edit Valid - stable 2022-08-11 PLGW2000154
euProtectedAreaCode.PLGW2000156 156 Quick edit Valid - stable 2022-08-11 PLGW2000156
euProtectedAreaCode.PLGW2000157 157 Quick edit Valid - stable 2022-08-11 PLGW2000157
euProtectedAreaCode.PLGW2000158 158 Quick edit Valid - stable 2022-08-11 PLGW2000158
euProtectedAreaCode.PLGW2000159 159 Quick edit Valid - stable 2022-08-11 PLGW2000159
euProtectedAreaCode.PLGW200016 16 Quick edit Valid - stable 2022-08-11 PLGW200016
euProtectedAreaCode.PLGW2000160 160 Quick edit Valid - stable 2022-08-11 PLGW2000160
euProtectedAreaCode.PLGW2000161 161 Quick edit Valid - stable 2022-08-11 PLGW2000161
euProtectedAreaCode.PLGW2000162 162 Quick edit Valid - stable 2022-08-11 PLGW2000162
euProtectedAreaCode.PLGW2000163 163 Quick edit Valid - stable 2022-08-11 PLGW2000163
euProtectedAreaCode.PLGW2000165 165 Quick edit Valid - stable 2022-08-11 PLGW2000165
euProtectedAreaCode.PLGW2000166 166 Quick edit Valid - stable 2022-08-11 PLGW2000166
euProtectedAreaCode.PLGW2000167 167 Quick edit Valid - stable 2022-08-11 PLGW2000167
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?