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 96,901 to 96,920.First4,8424,8434,8444,8454,8464,8474,8484,849Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL396192 KO?O W PUSZCZY NIEPO?OMICKIEJ Quick edit Valid - stable 2022-08-11 PL396192
euProtectedAreaCode.PL396193 KO?SKIE B?OTA Quick edit Valid - stable 2022-08-11 PL396193
euProtectedAreaCode.PL396194 KOZINIEC Quick edit Valid - stable 2022-08-11 PL396194
euProtectedAreaCode.PL396195 BAGNO G?USZA Quick edit Valid - stable 2022-08-11 PL396195
euProtectedAreaCode.PL396196 BUKOWSKIE BAGNO Quick edit Valid - stable 2022-08-11 PL396196
euProtectedAreaCode.PL396197 CZARNE BAGNO Quick edit Valid - stable 2022-08-11 PL396197
euProtectedAreaCode.PL396198 CZARNE STAWY Quick edit Valid - stable 2022-08-11 PL396198
euProtectedAreaCode.PL396199 CZESZEWSKI LAS Quick edit Valid - stable 2022-08-11 PL396199
euProtectedAreaCode.PL396200 D?BY BIESIADNE IM. MARIANA PULKOWSKIEGO Quick edit Valid - stable 2022-08-11 PL396200
euProtectedAreaCode.PL396201 DIABELSKIE PUSTACIE Quick edit Valid - stable 2022-08-11 PL396201
euProtectedAreaCode.PL396202 D?UGOSZ KRÓLEWSKI W WIERZCHUCINIE Quick edit Valid - stable 2022-08-11 PL396202
euProtectedAreaCode.PL396203 DOLINA HUCZKA Quick edit Valid - stable 2022-08-11 PL396203
euProtectedAreaCode.PL396204 DOLINA KAMIONKI Quick edit Valid - stable 2022-08-11 PL396204
euProtectedAreaCode.PL396205 DOLINA POSTOMII Quick edit Valid - stable 2022-08-11 PL396205
euProtectedAreaCode.PL396206 DOLINA STRADANKI Quick edit Valid - stable 2022-08-11 PL396206
euProtectedAreaCode.PL396207 DOLINA STRZY?Y Quick edit Valid - stable 2022-08-11 PL396207
euProtectedAreaCode.PL396208 KRZEMIE?SKIE ?RÓDLISKA Quick edit Valid - stable 2022-08-11 PL396208
euProtectedAreaCode.PL396209 KRZYWICKI MSZAR Quick edit Valid - stable 2022-08-11 PL396209
euProtectedAreaCode.PL396210 KWIECEWO Quick edit Valid - stable 2022-08-11 PL396210
euProtectedAreaCode.PL396211 LAS D?BROWA Quick edit Valid - stable 2022-08-11 PL396211
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?