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,481 to 4,500.First221222223224225226227228Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBW_PR_0194 BAINDT BADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0194
euProtectedAreaCode.DEBW_PR_0195 EBENWEILER EBENWEILERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0195
euProtectedAreaCode.DEBW_PR_0196 FRONREUTE BIBERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0196
euProtectedAreaCode.DEBW_PR_0197 FRONREUTE HAECKLERWEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0197
euProtectedAreaCode.DEBW_PR_0198 MOELLENBRONN BAGGERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0198
euProtectedAreaCode.DEBW_PR_0199 KOENIGSEGGSEE HOSSKIRCHER STRAND Quick edit Valid - stable 2025-01-29 DEBW_PR_0199
euProtectedAreaCode.DEBW_PR_0200 ISNY BAGGERSEE BURKWANG Quick edit Valid - stable 2025-01-29 DEBW_PR_0200
euProtectedAreaCode.DEBW_PR_0201 ISNY WALDBAD Quick edit Valid - stable 2025-01-29 DEBW_PR_0201
euProtectedAreaCode.DEBW_PR_0202 BEUREN BADESEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0202
euProtectedAreaCode.DEBW_PR_0203 KISSLEGG HOLZMUEHLEWEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0203
euProtectedAreaCode.DEBW_PR_0204 KISSLEGG ARGENSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0204
euProtectedAreaCode.DEBW_PR_0205 KISSLEGG FREIBAD OBERSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0205
euProtectedAreaCode.DEBW_PR_0206 LEUTKIRCH ELLERAZHOFER WEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0206
euProtectedAreaCode.DEBW_PR_0207 LEUTKIRCH STADTWEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0207
euProtectedAreaCode.DEBW_PR_0208 HERLAZHOFEN MOORBAD Quick edit Valid - stable 2025-01-29 DEBW_PR_0208
euProtectedAreaCode.DEBW_PR_0209 RAVENSBURG FLAPPACHWEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0209
euProtectedAreaCode.DEBW_PR_0210 SCHLIER ROESSLERWEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0210
euProtectedAreaCode.DEBW_PR_0211 VOGT HOLZMUEHLEWEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0211
euProtectedAreaCode.DEBW_PR_0212 WANGEN BLAUSEE Quick edit Valid - stable 2025-01-29 DEBW_PR_0212
euProtectedAreaCode.DEBW_PR_0213 WANGEN KARSEE WEIHER Quick edit Valid - stable 2025-01-29 DEBW_PR_0213
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?