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,256 concepts found, displaying 6,021 to 6,040.First298299300301302303304305Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEPE_NWF001 AGGERTALSPERRE Quick edit Valid - stable 2025-01-29 DEPE_NWF001
euProtectedAreaCode.DEPE_NWF002 AGGER Quick edit Valid - stable 2025-01-29 DEPE_NWF002
euProtectedAreaCode.DEPE_NWF003 AHR Quick edit Valid - stable 2025-01-29 DEPE_NWF003
euProtectedAreaCode.DEPE_NWF004 ALME Quick edit Valid - stable 2025-01-29 DEPE_NWF004
euProtectedAreaCode.DEPE_NWF005 AHAUSER AA Quick edit Valid - stable 2025-01-29 DEPE_NWF005
euProtectedAreaCode.DEPE_NWF006 BEGA Quick edit Valid - stable 2025-01-29 DEPE_NWF006
euProtectedAreaCode.DEPE_NWF007 BERKEL Quick edit Valid - stable 2025-01-29 DEPE_NWF007
euProtectedAreaCode.DEPE_NWF008 BEVER Quick edit Valid - stable 2025-01-29 DEPE_NWF008
euProtectedAreaCode.DEPE_NWF009 BIGGETALSPERRE Quick edit Valid - stable 2025-01-29 DEPE_NWF009
euProtectedAreaCode.DEPE_NWF010 BOCHOLTER AA Quick edit Valid - stable 2025-01-29 DEPE_NWF010
euProtectedAreaCode.DEPE_NWF011 DIEMEL Quick edit Valid - stable 2025-01-29 DEPE_NWF011
euProtectedAreaCode.DEPE_NWF012 DINKEL Quick edit Valid - stable 2025-01-29 DEPE_NWF012
euProtectedAreaCode.DEPE_NWF013 EDER Quick edit Valid - stable 2025-01-29 DEPE_NWF013
euProtectedAreaCode.DEPE_NWF014 ELSE Quick edit Valid - stable 2025-01-29 DEPE_NWF014
euProtectedAreaCode.DEPE_NWF015 EMMER Quick edit Valid - stable 2025-01-29 DEPE_NWF015
euProtectedAreaCode.DEPE_NWF016 EMS Quick edit Valid - stable 2025-01-29 DEPE_NWF016
euProtectedAreaCode.DEPE_NWF017 EMS Quick edit Valid - stable 2025-01-29 DEPE_NWF017
euProtectedAreaCode.DEPE_NWF018 ENNEPETALSPERRE Quick edit Valid - stable 2025-01-29 DEPE_NWF018
euProtectedAreaCode.DEPE_NWF019 ERFT Quick edit Valid - stable 2025-01-29 DEPE_NWF019
euProtectedAreaCode.DEPE_NWF020 ERFT Quick edit Valid - stable 2025-01-29 DEPE_NWF020
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?