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,781 to 95,800.First4,7864,7874,7884,7894,7904,7914,7924,793Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL116171 ??G NA K?PIE W PU?AWACH Quick edit Valid - stable 2022-08-11 PL116171
euProtectedAreaCode.PL116172 ??GI CZARNEJ STRUGI Quick edit Valid - stable 2022-08-11 PL116172
euProtectedAreaCode.PL116173 ??GI OBORSKIE- W WERYFIKACJI Quick edit Valid - stable 2022-08-11 PL116173
euProtectedAreaCode.PL116174 ???CZOK Quick edit Valid - stable 2022-08-11 PL116174
euProtectedAreaCode.PL116175 ?OKIE? Quick edit Valid - stable 2022-08-11 PL116175
euProtectedAreaCode.PL116177 ?OSIOWE B?OTA Quick edit Valid - stable 2022-08-11 PL116177
euProtectedAreaCode.PL116178 ?O? Quick edit Valid - stable 2022-08-11 PL116178
euProtectedAreaCode.PL116179 ?UGI Quick edit Valid - stable 2022-08-11 PL116179
euProtectedAreaCode.PL116180 ?UGI HELENOWSKIE Quick edit Valid - stable 2022-08-11 PL116180
euProtectedAreaCode.PL116181 ?UNIEWO Quick edit Valid - stable 2022-08-11 PL116181
euProtectedAreaCode.PL116182 ?USZCZANOWICE Quick edit Valid - stable 2022-08-11 PL116182
euProtectedAreaCode.PL116183 MADOHORA Quick edit Valid - stable 2022-08-11 PL116183
euProtectedAreaCode.PL116184 MAJÓWKA Quick edit Valid - stable 2022-08-11 PL116184
euProtectedAreaCode.PL116185 MA?ECZ Quick edit Valid - stable 2022-08-11 PL116185
euProtectedAreaCode.PL116186 MA?GA Quick edit Valid - stable 2022-08-11 PL116186
euProtectedAreaCode.PL116187 MA?OZIEMCE Quick edit Valid - stable 2022-08-11 PL116187
euProtectedAreaCode.PL11631 I?SKI PARK KRAJOBRAZOWY Quick edit Valid - stable 2022-08-11 PL11631
euProtectedAreaCode.PL11632 KASZUBSKI PARK KRAJOBRAZOWY Quick edit Valid - stable 2022-08-11 PL11632
euProtectedAreaCode.PL11634 KSI??A?SKI PARK KRAJOBRAZOWY Quick edit Valid - stable 2022-08-11 PL11634
euProtectedAreaCode.PL11635 ?NIE?NICKI PARK KRAJOBRAZOWY Quick edit Valid - stable 2022-08-11 PL11635
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?