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,281 to 96,300.First4,8114,8124,8134,8144,8154,8164,8174,818Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL177327 D?BY KRAJE?SKIE Quick edit Valid - stable 2022-08-11 PL177327
euProtectedAreaCode.PL177328 D?BY W KRUKACH PAS??CKICH Quick edit Valid - stable 2022-08-11 PL177328
euProtectedAreaCode.PL177329 DOLINA RZEKI BRDY Quick edit Valid - stable 2022-08-11 PL177329
euProtectedAreaCode.PL177330 DOLINA CH?APOWSKA Quick edit Valid - stable 2022-08-11 PL177330
euProtectedAreaCode.PL177331 DOLINA GWDY Quick edit Valid - stable 2022-08-11 PL177331
euProtectedAreaCode.PL177332 DOLINA ILANKI Quick edit Valid - stable 2022-08-11 PL177332
euProtectedAreaCode.PL177333 DOLINA K?ODAWY Quick edit Valid - stable 2022-08-11 PL177333
euProtectedAreaCode.PL177334 DOLINA ?A?SKIEGO POTOKU Quick edit Valid - stable 2022-08-11 PL177334
euProtectedAreaCode.PL177335 DOLINA M?AWKI Quick edit Valid - stable 2022-08-11 PL177335
euProtectedAreaCode.PL177336 DOLINA OSY Quick edit Valid - stable 2022-08-11 PL177336
euProtectedAreaCode.PL177337 DOLINA POTOKU RUDNO Quick edit Valid - stable 2022-08-11 PL177337
euProtectedAreaCode.PL177338 DOLINA WALICZÓWKI Quick edit Valid - stable 2022-08-11 PL177338
euProtectedAreaCode.PL177339 DOLINA ?ABNIKA Quick edit Valid - stable 2022-08-11 PL177339
euProtectedAreaCode.PL177340 DO?Y SZCZECKIE Quick edit Valid - stable 2022-08-11 PL177340
euProtectedAreaCode.PL177342 DYRBEK Quick edit Valid - stable 2022-08-11 PL177342
euProtectedAreaCode.PL177343 DZIER?ENI?SKA K?PA Quick edit Valid - stable 2022-08-11 PL177343
euProtectedAreaCode.PL177344 DZIKI STAW Quick edit Valid - stable 2022-08-11 PL177344
euProtectedAreaCode.PL177345 DZIOBAKI Quick edit Valid - stable 2022-08-11 PL177345
euProtectedAreaCode.PL177346 GAGATY SO?TYKOWSKIE Quick edit Valid - stable 2022-08-11 PL177346
euProtectedAreaCode.PL177347 GAWRONIEC Quick edit Valid - stable 2022-08-11 PL177347
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?