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,921 to 96,940.First4,8434,8444,8454,8464,8474,8484,8494,850Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL396212 LAS M?TAWSKI Quick edit Valid - stable 2022-08-11 PL396212
euProtectedAreaCode.PL396213 LAS MINIKOWSKI Quick edit Valid - stable 2022-08-11 PL396213
euProtectedAreaCode.PL396214 LASY NATURALNE PUSZCZY BIA?OWIESKIEJ Quick edit Valid - stable 2022-08-11 PL396214
euProtectedAreaCode.PL396215 LIPOWSKA Quick edit Valid - stable 2022-08-11 PL396215
euProtectedAreaCode.PL396216 LIWOCZ Quick edit Valid - stable 2022-08-11 PL396216
euProtectedAreaCode.PL396217 ?AZY Quick edit Valid - stable 2022-08-11 PL396217
euProtectedAreaCode.PL396218 ?A?YN Quick edit Valid - stable 2022-08-11 PL396218
euProtectedAreaCode.PL396219 ?EBSKIE BAGNO Quick edit Valid - stable 2022-08-11 PL396219
euProtectedAreaCode.PL396220 ??G NAD M?YNÓWK? Quick edit Valid - stable 2022-08-11 PL396220
euProtectedAreaCode.PL396221 ??G NAD SWELINI? Quick edit Valid - stable 2022-08-11 PL396221
euProtectedAreaCode.PL396222 ??GI KO?O S?UBIC Quick edit Valid - stable 2022-08-11 PL396222
euProtectedAreaCode.PL396223 ?YSA GÓRA Quick edit Valid - stable 2022-08-11 PL396223
euProtectedAreaCode.PL396224 MECHOWISKA CZAPLE Quick edit Valid - stable 2022-08-11 PL396224
euProtectedAreaCode.PL396225 MIERKOWSKIE SUCHE BORY Quick edit Valid - stable 2022-08-11 PL396225
euProtectedAreaCode.PL396226 MIERZWICE Quick edit Valid - stable 2022-08-11 PL396226
euProtectedAreaCode.PL396227 MOCZARY Quick edit Valid - stable 2022-08-11 PL396227
euProtectedAreaCode.PL396228 MOKRY JEGIEL Quick edit Valid - stable 2022-08-11 PL396228
euProtectedAreaCode.PL396229 MSZAR PRZYGIE?KOWY – D?UGIE IM. HUBERTA JURCZYSZYNA Quick edit Valid - stable 2022-08-11 PL396229
euProtectedAreaCode.PL396230 MSZAR ROSICZKOWY KO?O ROKITNA Quick edit Valid - stable 2022-08-11 PL396230
euProtectedAreaCode.PL396231 NAD JEZIOREM LIPTOWSKIM Quick edit Valid - stable 2022-08-11 PL396231
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?