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,301 to 135,320.First6,7626,7636,7646,7656,7666,7676,7686,769Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SIOBC18 POD VIDMOM Quick edit Valid - stable 2025-01-29 SIOBC18
euProtectedAreaCode.SIOBC19 GLOBOSCAK Quick edit Valid - stable 2025-01-29 SIOBC19
euProtectedAreaCode.SIOBC2 POD OVCJAKOM Quick edit Valid - stable 2025-01-29 SIOBC2
euProtectedAreaCode.SIOBC2001 NADIZA Quick edit Valid - stable 2025-01-29 SIOBC2001
euProtectedAreaCode.SIOBC2002 KOREN Quick edit Valid - stable 2025-01-29 SIOBC2002
euProtectedAreaCode.SIOBC2003 ZELEZNISKO Quick edit Valid - stable 2025-01-29 SIOBC2003
euProtectedAreaCode.SIOBC2004 LOG Quick edit Valid - stable 2025-01-29 SIOBC2004
euProtectedAreaCode.SIOBC2005 ZAGMAJNICA Quick edit Valid - stable 2025-01-29 SIOBC2005
euProtectedAreaCode.SIOBC2006 JASNA Quick edit Valid - stable 2025-01-29 SIOBC2006
euProtectedAreaCode.SIOBC2007 CRNA VODA Quick edit Valid - stable 2025-01-29 SIOBC2007
euProtectedAreaCode.SIOBC2008 MIHOV DOM Quick edit Valid - stable 2025-01-29 SIOBC2008
euProtectedAreaCode.SIOBC2009 KOCA NA GOZDU Quick edit Valid - stable 2025-01-29 SIOBC2009
euProtectedAreaCode.SIOBC2010 ERJAVCEVA KOCA Quick edit Valid - stable 2025-01-29 SIOBC2010
euProtectedAreaCode.SIOBC2011 VRTINE JUREZ Quick edit Valid - stable 2025-01-29 SIOBC2011
euProtectedAreaCode.SIOBC2012 BELI POTOK Quick edit Valid - stable 2025-01-29 SIOBC2012
euProtectedAreaCode.SIOBC2013 ALJAZEV DOM Quick edit Valid - stable 2025-01-29 SIOBC2013
euProtectedAreaCode.SIOBC2014 BELCA Quick edit Valid - stable 2025-01-29 SIOBC2014
euProtectedAreaCode.SIOBC2015 DOLINA MALA PISNICA Quick edit Valid - stable 2025-01-29 SIOBC2015
euProtectedAreaCode.SIOBC2016 JENCNOVO Quick edit Valid - stable 2025-01-29 SIOBC2016
euProtectedAreaCode.SIOBC2018 VAPS Quick edit Valid - stable 2025-01-29 SIOBC2018
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?