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 95,761 to 95,780.First4,7854,7864,7874,7884,7894,7904,7914,792Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL116150 LISKI Quick edit Valid - stable 2022-08-11 PL116150
euProtectedAreaCode.PL116151 LISKI I Quick edit Valid - stable 2022-08-11 PL116151
euProtectedAreaCode.PL116152 LUBATY Quick edit Valid - stable 2022-08-11 PL116152
euProtectedAreaCode.PL116153 LUBCZA Quick edit Valid - stable 2022-08-11 PL116153
euProtectedAreaCode.PL116154 LUBIASZÓW Quick edit Valid - stable 2022-08-11 PL116154
euProtectedAreaCode.PL116155 LUBO? WIELKI Quick edit Valid - stable 2022-08-11 PL116155
euProtectedAreaCode.PL116156 LUBSZA Quick edit Valid - stable 2022-08-11 PL116156
euProtectedAreaCode.PL116157 LUCIE? Quick edit Valid - stable 2022-08-11 PL116157
euProtectedAreaCode.PL116158 LUPA Quick edit Valid - stable 2022-08-11 PL116158
euProtectedAreaCode.PL116160 ?AB?DZINIEC Quick edit Valid - stable 2022-08-11 PL116160
euProtectedAreaCode.PL116161 ?AB?D? Quick edit Valid - stable 2022-08-11 PL116161
euProtectedAreaCode.PL116162 ?ABOWIEC Quick edit Valid - stable 2022-08-11 PL116162
euProtectedAreaCode.PL116163 ?ABUNIE Quick edit Valid - stable 2022-08-11 PL116163
euProtectedAreaCode.PL116164 ?ACHA JELCZ Quick edit Valid - stable 2022-08-11 PL116164
euProtectedAreaCode.PL116165 ?ASKO Quick edit Valid - stable 2022-08-11 PL116165
euProtectedAreaCode.PL116166 ?AZNÓW Quick edit Valid - stable 2022-08-11 PL116166
euProtectedAreaCode.PL116167 ??KA SULISTROWICKA Quick edit Valid - stable 2022-08-11 PL116167
euProtectedAreaCode.PL116168 ??KI ?LESI?SKIE Quick edit Valid - stable 2022-08-11 PL116168
euProtectedAreaCode.PL116169 ?EMPIS Quick edit Valid - stable 2022-08-11 PL116169
euProtectedAreaCode.PL116170 ??G D?BOWY KO?O JANOWA PODLASKIEGO Quick edit Valid - stable 2022-08-11 PL116170
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?