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 4,261 to 4,280.First210211212213214215216217Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBE_PR_0013 STRANDBAD LUEBARS Quick edit Valid - stable 2025-01-29 DEBE_PR_0013
euProtectedAreaCode.DEBE_PR_0014 OBERHAVEL BUERGERABLAGE Quick edit Valid - stable 2025-01-29 DEBE_PR_0014
euProtectedAreaCode.DEBE_PR_0015 UNTERHAVEL KLEINE BADEWIESE Quick edit Valid - stable 2025-01-29 DEBE_PR_0015
euProtectedAreaCode.DEBE_PR_0016 STRANDBAD PLOETZENSEE Quick edit Valid - stable 2025-01-29 DEBE_PR_0016
euProtectedAreaCode.DEBE_PR_0017 UNTERHAVEL GROSSE STEINLANKE Quick edit Valid - stable 2025-01-29 DEBE_PR_0017
euProtectedAreaCode.DEBE_PR_0018 STRANDBAD WANNSEE Quick edit Valid - stable 2025-01-29 DEBE_PR_0018
euProtectedAreaCode.DEBE_PR_0019 FLUGHAFENSEE Quick edit Valid - stable 2025-01-29 DEBE_PR_0019
euProtectedAreaCode.DEBE_PR_0020 GROSS GLIENICKER SEE NOERDLICH Quick edit Valid - stable 2025-01-29 DEBE_PR_0020
euProtectedAreaCode.DEBE_PR_0021 GROSS GLIENICKER SEE SUEDLICH Quick edit Valid - stable 2025-01-29 DEBE_PR_0021
euProtectedAreaCode.DEBE_PR_0022 SCHLACHTENSEE Quick edit Valid - stable 2025-01-29 DEBE_PR_0022
euProtectedAreaCode.DEBE_PR_0023 KRUMME LANKE Quick edit Valid - stable 2025-01-29 DEBE_PR_0023
euProtectedAreaCode.DEBE_PR_0024 FREIBAD HALENSEE Quick edit Valid - stable 2025-01-29 DEBE_PR_0024
euProtectedAreaCode.DEBE_PR_0025 UNTERHAVEL ALTER HOF Quick edit Valid - stable 2025-01-29 DEBE_PR_0025
euProtectedAreaCode.DEBE_PR_0026 UNTERHAVEL BREITEHORN Quick edit Valid - stable 2025-01-29 DEBE_PR_0026
euProtectedAreaCode.DEBE_PR_0027 DAEMERITZSEE Quick edit Valid - stable 2025-01-29 DEBE_PR_0027
euProtectedAreaCode.DEBE_PR_0028 FLUSSBAD GARTENSTRASSE Quick edit Valid - stable 2025-01-29 DEBE_PR_0028
euProtectedAreaCode.DEBE_PR_0029 GROSSE KRAMPE Quick edit Valid - stable 2025-01-29 DEBE_PR_0029
euProtectedAreaCode.DEBE_PR_0030 UNTERHAVEL GRUNEWALDTURM Quick edit Valid - stable 2025-01-29 DEBE_PR_0030
euProtectedAreaCode.DEBE_PR_0031 FREIBAD HEILIGENSEE Quick edit Valid - stable 2025-01-29 DEBE_PR_0031
euProtectedAreaCode.DEBE_PR_0032 UNTERHAVEL LIEPER BUCHT Quick edit Valid - stable 2025-01-29 DEBE_PR_0032
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?