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 104,261 to 104,280.First5,2105,2115,2125,2135,2145,2155,2165,217Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SIOBC5052 RA-2/85 Quick edit Valid - stable 2022-08-11 SIOBC5052
euProtectedAreaCode.SIOBC5060 RABZELJ Quick edit Valid - stable 2022-08-11 SIOBC5060
euProtectedAreaCode.SIOBC5063 BU?KA Quick edit Valid - stable 2022-08-11 SIOBC5063
euProtectedAreaCode.SIOBC5064 Š?ETAR Quick edit Valid - stable 2022-08-11 SIOBC5064
euProtectedAreaCode.SIOBC51 PADEŽ Quick edit Valid - stable 2022-08-11 SIOBC51
euProtectedAreaCode.SIOBC5200 MIRNA Quick edit Valid - stable 2022-08-11 SIOBC5200
euProtectedAreaCode.SIOBC5201 BA?JI POTOK Quick edit Valid - stable 2022-08-11 SIOBC5201
euProtectedAreaCode.SIOBC5202 MIRNA DOLINA Quick edit Valid - stable 2022-08-11 SIOBC5202
euProtectedAreaCode.SIOBC5203 RAVNE Quick edit Valid - stable 2022-08-11 SIOBC5203
euProtectedAreaCode.SIOBC5204 ŠKRJAN?E - ŠEVNICA Quick edit Valid - stable 2022-08-11 SIOBC5204
euProtectedAreaCode.SIOBC5205 SELO PRI MIRNI Quick edit Valid - stable 2022-08-11 SIOBC5205
euProtectedAreaCode.SIOBC5206 MIGOLICA - MIGOLSKA GORA Quick edit Valid - stable 2022-08-11 SIOBC5206
euProtectedAreaCode.SIOBC5207 RAVNIK - ŠKRILEJEVO Quick edit Valid - stable 2022-08-11 SIOBC5207
euProtectedAreaCode.SIOBC5208 ŠENTRUPERT Quick edit Valid - stable 2022-08-11 SIOBC5208
euProtectedAreaCode.SIOBC5209 HRASTNO Quick edit Valid - stable 2022-08-11 SIOBC5209
euProtectedAreaCode.SIOBC5210 RODINE PRI TREBNJEM Quick edit Valid - stable 2022-08-11 SIOBC5210
euProtectedAreaCode.SIOBC5211 ?EŠNJICE Quick edit Valid - stable 2022-08-11 SIOBC5211
euProtectedAreaCode.SIOBC5212 ŠTATENBERK Quick edit Valid - stable 2022-08-11 SIOBC5212
euProtectedAreaCode.SIOBC5213 BREZJE PRI TREBELNEM Quick edit Valid - stable 2022-08-11 SIOBC5213
euProtectedAreaCode.SIOBC5214 TREBELNO - VRH PRI TREBELNEM Quick edit Valid - stable 2022-08-11 SIOBC5214
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?