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 103,781 to 103,800.First5,1865,1875,1885,1895,1905,1915,1925,193Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SIOBC4134 K-1/89 Quick edit Valid - stable 2022-08-11 SIOBC4134
euProtectedAreaCode.SIOBC4135 KOPRIVNIK Quick edit Valid - stable 2022-08-11 SIOBC4135
euProtectedAreaCode.SIOBC4136 KNEŽJA LIPA Quick edit Valid - stable 2022-08-11 SIOBC4136
euProtectedAreaCode.SIOBC4137 SL-1/90 Quick edit Valid - stable 2022-08-11 SIOBC4137
euProtectedAreaCode.SIOBC4138 PODKLANEC Quick edit Valid - stable 2022-08-11 SIOBC4138
euProtectedAreaCode.SIOBC4139 HRIB-ŽIMARICE Quick edit Valid - stable 2022-08-11 SIOBC4139
euProtectedAreaCode.SIOBC4141 ŽLEBEC Quick edit Valid - stable 2022-08-11 SIOBC4141
euProtectedAreaCode.SIOBC4142 KRŽETI 1 Quick edit Valid - stable 2022-08-11 SIOBC4142
euProtectedAreaCode.SIOBC4143 JELOVEC Quick edit Valid - stable 2022-08-11 SIOBC4143
euProtectedAreaCode.SIOBC4144 PODSTENE Quick edit Valid - stable 2022-08-11 SIOBC4144
euProtectedAreaCode.SIOBC4145 KOTEL Quick edit Valid - stable 2022-08-11 SIOBC4145
euProtectedAreaCode.SIOBC4146 LAŠ?EK Quick edit Valid - stable 2022-08-11 SIOBC4146
euProtectedAreaCode.SIOBC4147 DAVNO KORITO Quick edit Valid - stable 2022-08-11 SIOBC4147
euProtectedAreaCode.SIOBC4148 S-1 Quick edit Valid - stable 2022-08-11 SIOBC4148
euProtectedAreaCode.SIOBC4149 S-2 Quick edit Valid - stable 2022-08-11 SIOBC4149
euProtectedAreaCode.SIOBC4150 S-3 Quick edit Valid - stable 2022-08-11 SIOBC4150
euProtectedAreaCode.SIOBC4151 S-4 Quick edit Valid - stable 2022-08-11 SIOBC4151
euProtectedAreaCode.SIOBC4152 S-5 Quick edit Valid - stable 2022-08-11 SIOBC4152
euProtectedAreaCode.SIOBC4153 PODGORA Quick edit Valid - stable 2022-08-11 SIOBC4153
euProtectedAreaCode.SIOBC4155 ŠTEFANJA GORA-DAVOVEC Quick edit Valid - stable 2022-08-11 SIOBC4155
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?