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,541 to 96,560.First4,8244,8254,8264,8274,8284,8294,8304,831Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL177603 TORFOWISKO SERAFIN Quick edit Valid - stable 2022-08-11 PL177603
euProtectedAreaCode.PL177604 TR?BACZEW Quick edit Valid - stable 2022-08-11 PL177604
euProtectedAreaCode.PL177605 TRZY JEZIORA Quick edit Valid - stable 2022-08-11 PL177605
euProtectedAreaCode.PL177606 TURNICA Quick edit Valid - stable 2022-08-11 PL177606
euProtectedAreaCode.PL177607 ULÓW Quick edit Valid - stable 2022-08-11 PL177607
euProtectedAreaCode.PL177608 UROCZYSKO DZIERZBA Quick edit Valid - stable 2022-08-11 PL177608
euProtectedAreaCode.PL177609 UROCZYSKO JARY Quick edit Valid - stable 2022-08-11 PL177609
euProtectedAreaCode.PL177610 UROCZYSKO KRAMNIK Quick edit Valid - stable 2022-08-11 PL177610
euProtectedAreaCode.PL177611 UROCZYSKO PIOTROWICE Quick edit Valid - stable 2022-08-11 PL177611
euProtectedAreaCode.PL177612 UROCZYSKO WRZOSY Quick edit Valid - stable 2022-08-11 PL177612
euProtectedAreaCode.PL177613 W?WÓZ LIPA Quick edit Valid - stable 2022-08-11 PL177613
euProtectedAreaCode.PL177614 W?WÓZ SIEDMICKI Quick edit Valid - stable 2022-08-11 PL177614
euProtectedAreaCode.PL177615 W?WÓZ W SKA?ACH Quick edit Valid - stable 2022-08-11 PL177615
euProtectedAreaCode.PL177616 WIDOWO Quick edit Valid - stable 2022-08-11 PL177616
euProtectedAreaCode.PL177618 WIELKI DZIA? Quick edit Valid - stable 2022-08-11 PL177618
euProtectedAreaCode.PL177619 WIELKI LAS Quick edit Valid - stable 2022-08-11 PL177619
euProtectedAreaCode.PL177620 WIELKOPOLE Quick edit Valid - stable 2022-08-11 PL177620
euProtectedAreaCode.PL177621 WIETRZNIA IM. Z. RUBINOWSKIEGO Quick edit Valid - stable 2022-08-11 PL177621
euProtectedAreaCode.PL177622 WIKLINY WI?LANE Quick edit Valid - stable 2022-08-11 PL177622
euProtectedAreaCode.PL177623 WILCZE Quick edit Valid - stable 2022-08-11 PL177623
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?