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 97,901 to 97,920.First4,8924,8934,8944,8954,8964,8974,8984,899Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL851 BIESZCZADZKI PARK NARODOWY Quick edit Valid - stable 2022-08-11 PL851
euProtectedAreaCode.PL852 KARKONOSKI PARK NARODOWY Quick edit Valid - stable 2022-08-11 PL852
euProtectedAreaCode.PL853 WIELKOPOLSKI PARK NARODOWY Quick edit Valid - stable 2022-08-11 PL853
euProtectedAreaCode.PL854 BIA?OWIESKI PARK NARODOWY Quick edit Valid - stable 2022-08-11 PL854
euProtectedAreaCode.PL855 WOLI?SKI PARK NARODOWY Quick edit Valid - stable 2022-08-11 PL855
euProtectedAreaCode.PL856 ROZTOCZA?SKI PARK NARODOWY Quick edit Valid - stable 2022-08-11 PL856
euProtectedAreaCode.PL857 PIENI?SKI PARK NARODOWY Quick edit Valid - stable 2022-08-11 PL857
euProtectedAreaCode.PL859 OJCOWSKI PARK NARODOWY Quick edit Valid - stable 2022-08-11 PL859
euProtectedAreaCode.PLGW1000164 164 Quick edit Valid - stable 2022-08-11 PLGW1000164
euProtectedAreaCode.PLGW1000171 171 Quick edit Valid - stable 2022-08-11 PLGW1000171
euProtectedAreaCode.PLGW2000100 100 Quick edit Valid - stable 2022-08-11 PLGW2000100
euProtectedAreaCode.PLGW2000101 101 Quick edit Valid - stable 2022-08-11 PLGW2000101
euProtectedAreaCode.PLGW2000102 102 Quick edit Valid - stable 2022-08-11 PLGW2000102
euProtectedAreaCode.PLGW2000103 103 Quick edit Valid - stable 2022-08-11 PLGW2000103
euProtectedAreaCode.PLGW2000104 104 Quick edit Valid - stable 2022-08-11 PLGW2000104
euProtectedAreaCode.PLGW200011 11 Quick edit Valid - stable 2022-08-11 PLGW200011
euProtectedAreaCode.PLGW2000111 111 Quick edit Valid - stable 2022-08-11 PLGW2000111
euProtectedAreaCode.PLGW2000112 112 Quick edit Valid - stable 2022-08-11 PLGW2000112
euProtectedAreaCode.PLGW2000113 113 Quick edit Valid - stable 2022-08-11 PLGW2000113
euProtectedAreaCode.PLGW2000114 114 Quick edit Valid - stable 2022-08-11 PLGW2000114
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?