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,961 to 103,980.First5,1955,1965,1975,1985,1995,2005,2015,202Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SIOBC4496 HITENO Quick edit Valid - stable 2022-08-11 SIOBC4496
euProtectedAreaCode.SIOBC4498 HITENO 3 Quick edit Valid - stable 2022-08-11 SIOBC4498
euProtectedAreaCode.SIOBC4499 JERŠANOVO Quick edit Valid - stable 2022-08-11 SIOBC4499
euProtectedAreaCode.SIOBC4500 LOVRANOVO Quick edit Valid - stable 2022-08-11 SIOBC4500
euProtectedAreaCode.SIOBC4501 ANDREJ?JE Quick edit Valid - stable 2022-08-11 SIOBC4501
euProtectedAreaCode.SIOBC4503 VELIKE BLOKE Quick edit Valid - stable 2022-08-11 SIOBC4503
euProtectedAreaCode.SIOBC4504 VELIKE BLOKE Quick edit Valid - stable 2022-08-11 SIOBC4504
euProtectedAreaCode.SIOBC4505 VELIKE BLOKE Quick edit Valid - stable 2022-08-11 SIOBC4505
euProtectedAreaCode.SIOBC4506 VELIKE BLOKE Quick edit Valid - stable 2022-08-11 SIOBC4506
euProtectedAreaCode.SIOBC4507 RAVNE, TOPOL Quick edit Valid - stable 2022-08-11 SIOBC4507
euProtectedAreaCode.SIOBC4508 ROŽAN?E Quick edit Valid - stable 2022-08-11 SIOBC4508
euProtectedAreaCode.SIOBC4509 RUNARSKO Quick edit Valid - stable 2022-08-11 SIOBC4509
euProtectedAreaCode.SIOBC4510 ŠIV?E Quick edit Valid - stable 2022-08-11 SIOBC4510
euProtectedAreaCode.SIOBC4511 ŠTOROVO, GRADIŠKA Quick edit Valid - stable 2022-08-11 SIOBC4511
euProtectedAreaCode.SIOBC4512 TOPOL Quick edit Valid - stable 2022-08-11 SIOBC4512
euProtectedAreaCode.SIOBC4513 VELIKE BLOKE Quick edit Valid - stable 2022-08-11 SIOBC4513
euProtectedAreaCode.SIOBC4514 ULAKA 2 Quick edit Valid - stable 2022-08-11 SIOBC4514
euProtectedAreaCode.SIOBC4515 VELIKI VRH Quick edit Valid - stable 2022-08-11 SIOBC4515
euProtectedAreaCode.SIOBC4516 VOL?JE Quick edit Valid - stable 2022-08-11 SIOBC4516
euProtectedAreaCode.SIOBC4517 BO?KOVO - ZALES Quick edit Valid - stable 2022-08-11 SIOBC4517
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?