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
22 Nov 2024
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

138,317 concepts found, displaying 135,521 to 135,540.First6,7736,7746,7756,7766,7776,7786,7796,780Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SIOBC4016 ZAGA-GORA Quick edit Valid - stable 2025-01-29 SIOBC4016
euProtectedAreaCode.SIOBC4017 CIGANKA Quick edit Valid - stable 2025-01-29 SIOBC4017
euProtectedAreaCode.SIOBC4018 STUDENCEVKA Quick edit Valid - stable 2025-01-29 SIOBC4018
euProtectedAreaCode.SIOBC4019 KUPARJEVO Quick edit Valid - stable 2025-01-29 SIOBC4019
euProtectedAreaCode.SIOBC4020 RD-1-01 Quick edit Valid - stable 2025-01-29 SIOBC4020
euProtectedAreaCode.SIOBC4021 GLOBOCEC Quick edit Valid - stable 2025-01-29 SIOBC4021
euProtectedAreaCode.SIOBC4022 VELIKA LOKA 1 Quick edit Valid - stable 2025-01-29 SIOBC4022
euProtectedAreaCode.SIOBC4023 VELIKA LOKA 2 Quick edit Valid - stable 2025-01-29 SIOBC4023
euProtectedAreaCode.SIOBC4024 K-1-96 -KOZELJEVEC Quick edit Valid - stable 2025-01-29 SIOBC4024
euProtectedAreaCode.SIOBC4025 VSP 2-97 Quick edit Valid - stable 2025-01-29 SIOBC4025
euProtectedAreaCode.SIOBC4027 ZGORNJA DRAGA Quick edit Valid - stable 2025-01-29 SIOBC4027
euProtectedAreaCode.SIOBC4028 VISNJA GORA Quick edit Valid - stable 2025-01-29 SIOBC4028
euProtectedAreaCode.SIOBC4039 L-43-V11045 VELIKA DOLINA Quick edit Valid - stable 2025-01-29 SIOBC4039
euProtectedAreaCode.SIOBC4040 MATJAZEV LAZ Quick edit Valid - stable 2025-01-29 SIOBC4040
euProtectedAreaCode.SIOBC4041 L-40 Quick edit Valid - stable 2025-01-29 SIOBC4041
euProtectedAreaCode.SIOBC4042 L-25 Quick edit Valid - stable 2025-01-29 SIOBC4042
euProtectedAreaCode.SIOBC4043 VG-10 Quick edit Valid - stable 2025-01-29 SIOBC4043
euProtectedAreaCode.SIOBC4044 VG-28 Quick edit Valid - stable 2025-01-29 SIOBC4044
euProtectedAreaCode.SIOBC4045 VG-13-V11091 JASTREBNIK Quick edit Valid - stable 2025-01-29 SIOBC4045
euProtectedAreaCode.SIOBC4046 AMBROZ POD KRVAVCEM Quick edit Valid - stable 2025-01-29 SIOBC4046
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?