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,241 to 96,260.First4,8094,8104,8114,8124,8134,8144,8154,816Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL177285 BOREK Quick edit Valid - stable 2022-08-11 PL177285
euProtectedAreaCode.PL177286 BO?E OKO Quick edit Valid - stable 2022-08-11 PL177286
euProtectedAreaCode.PL177287 BRODUSZURKI Quick edit Valid - stable 2022-08-11 PL177287
euProtectedAreaCode.PL177288 BRUNATNA GLEBA Quick edit Valid - stable 2022-08-11 PL177288
euProtectedAreaCode.PL177289 BREKINIA Quick edit Valid - stable 2022-08-11 PL177289
euProtectedAreaCode.PL177290 BRZYSKA WOLA Quick edit Valid - stable 2022-08-11 PL177290
euProtectedAreaCode.PL177291 BUCZYNA Quick edit Valid - stable 2022-08-11 PL177291
euProtectedAreaCode.PL177292 BUCZYNA JAKUBOWSKA Quick edit Valid - stable 2022-08-11 PL177292
euProtectedAreaCode.PL177293 BUCZYNA HELENOPOL Quick edit Valid - stable 2022-08-11 PL177293
euProtectedAreaCode.PL177294 BUCZYNA STORCZYKOWA NA BIA?YCH SKA?ACH Quick edit Valid - stable 2022-08-11 PL177294
euProtectedAreaCode.PL177295 BUCZYNA W WA?KOWEJ Quick edit Valid - stable 2022-08-11 PL177295
euProtectedAreaCode.PL177296 BUKI SUDECKIE Quick edit Valid - stable 2022-08-11 PL177296
euProtectedAreaCode.PL177297 BUKOWA K?PA Quick edit Valid - stable 2022-08-11 PL177297
euProtectedAreaCode.PL177298 BUKOWICA Quick edit Valid - stable 2022-08-11 PL177298
euProtectedAreaCode.PL177299 BUKOWY LAS Quick edit Valid - stable 2022-08-11 PL177299
euProtectedAreaCode.PL177300 CHELOSIOWA JAMA Quick edit Valid - stable 2022-08-11 PL177300
euProtectedAreaCode.PL177301 CHOMONTOWSZCZYZNA Quick edit Valid - stable 2022-08-11 PL177301
euProtectedAreaCode.PL177302 CHWANIÓW Quick edit Valid - stable 2022-08-11 PL177302
euProtectedAreaCode.PL177303 CICHA DOLINA Quick edit Valid - stable 2022-08-11 PL177303
euProtectedAreaCode.PL177304 CIECHOSTOWICE Quick edit Valid - stable 2022-08-11 PL177304
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?