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,141 to 135,160.First6,7546,7556,7566,7576,7586,7596,7606,761Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SIDRZ4320 J-4-02 Quick edit Valid - stable 2025-01-29 SIDRZ4320
euProtectedAreaCode.SIDRZ4323 ORLE 1 Quick edit Valid - stable 2025-01-29 SIDRZ4323
euProtectedAreaCode.SIDRZ4325 DOLE PRI SKOFLJICI 2 Quick edit Valid - stable 2025-01-29 SIDRZ4325
euProtectedAreaCode.SIDRZ4377 VD LIPOGLAV Quick edit Valid - stable 2025-01-29 SIDRZ4377
euProtectedAreaCode.SIDRZ4412 HRASTJE Quick edit Valid - stable 2025-01-29 SIDRZ4412
euProtectedAreaCode.SIDRZ4422 JARSKI PROD Quick edit Valid - stable 2025-01-29 SIDRZ4422
euProtectedAreaCode.SIDRZ4425 KLECE Quick edit Valid - stable 2025-01-29 SIDRZ4425
euProtectedAreaCode.SIDRZ4441 SENTVID Quick edit Valid - stable 2025-01-29 SIDRZ4441
euProtectedAreaCode.SIDRZ4488 LJUBLJANSKO POLJE Quick edit Valid - stable 2025-01-29 SIDRZ4488
euProtectedAreaCode.SIDRZ4519 DROBTINKA-BREZOVICA Quick edit Valid - stable 2025-01-29 SIDRZ4519
euProtectedAreaCode.SIDRZ4522 GOLA GORICA-BREZOVICA Quick edit Valid - stable 2025-01-29 SIDRZ4522
euProtectedAreaCode.SIDRZ4529 VZ-PODRESNIK Quick edit Valid - stable 2025-01-29 SIDRZ4529
euProtectedAreaCode.SIDRZ4637 VZ SUMNIK Quick edit Valid - stable 2025-01-29 SIDRZ4637
euProtectedAreaCode.SIDRZ4646 VD GORNJI IG Quick edit Valid - stable 2025-01-29 SIDRZ4646
euProtectedAreaCode.SIDRZ4647 KRVAVICA Quick edit Valid - stable 2025-01-29 SIDRZ4647
euProtectedAreaCode.SIDRZ4648 VV-1-86- VIRJE Quick edit Valid - stable 2025-01-29 SIDRZ4648
euProtectedAreaCode.SIDRZ4649 SUSA Quick edit Valid - stable 2025-01-29 SIDRZ4649
euProtectedAreaCode.SIDRZ4669 VD BREST-1 Quick edit Valid - stable 2025-01-29 SIDRZ4669
euProtectedAreaCode.SIDRZ4896 STAJE-GACNIK Quick edit Valid - stable 2025-01-29 SIDRZ4896
euProtectedAreaCode.SIDRZ4901 BEVKE Quick edit Valid - stable 2025-01-29 SIDRZ4901
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?