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,441 to 96,460.First4,8194,8204,8214,8224,8234,8244,8254,826Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL177498 OKÓLNY ?UG Quick edit Valid - stable 2022-08-11 PL177498
euProtectedAreaCode.PL177499 OLSZANKA Quick edit Valid - stable 2022-08-11 PL177499
euProtectedAreaCode.PL177500 OLSZANKA MY?LISZCZE Quick edit Valid - stable 2022-08-11 PL177500
euProtectedAreaCode.PL177501 OLSZYNY RUMOCKIE Quick edit Valid - stable 2022-08-11 PL177501
euProtectedAreaCode.PL177502 OLSY P?OSZYCKIE Quick edit Valid - stable 2022-08-11 PL177502
euProtectedAreaCode.PL177503 OSTNICOWE PAROWY GRUCZNA Quick edit Valid - stable 2022-08-11 PL177503
euProtectedAreaCode.PL177504 OSTRÓW TARCZY?SKI Quick edit Valid - stable 2022-08-11 PL177504
euProtectedAreaCode.PL177505 OWCZARY Quick edit Valid - stable 2022-08-11 PL177505
euProtectedAreaCode.PL177506 PARASZY?SKIE W?WOZY Quick edit Valid - stable 2022-08-11 PL177506
euProtectedAreaCode.PL177507 PAROWY JANINOWSKIE Quick edit Valid - stable 2022-08-11 PL177507
euProtectedAreaCode.PL177508 PATERAKI Quick edit Valid - stable 2022-08-11 PL177508
euProtectedAreaCode.PL177509 PAZA Quick edit Valid - stable 2022-08-11 PL177509
euProtectedAreaCode.PL177510 PE?CZNICA Quick edit Valid - stable 2022-08-11 PL177510
euProtectedAreaCode.PL177511 PERZOWA GÓRA Quick edit Valid - stable 2022-08-11 PL177511
euProtectedAreaCode.PL177512 PIECKI Quick edit Valid - stable 2022-08-11 PL177512
euProtectedAreaCode.PL177513 PIECZYSKA Quick edit Valid - stable 2022-08-11 PL177513
euProtectedAreaCode.PL177515 PIEKIE?KO Quick edit Valid - stable 2022-08-11 PL177515
euProtectedAreaCode.PL177516 PIEKIE?KO SZKUCKIE Quick edit Valid - stable 2022-08-11 PL177516
euProtectedAreaCode.PL177517 PIOTROWE POLE Quick edit Valid - stable 2022-08-11 PL177517
euProtectedAreaCode.PL177518 PISKORZENIEC Quick edit Valid - stable 2022-08-11 PL177518
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?