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 5,281 to 5,300.First261262263264265266267268Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEMV_PR_1_0802 GROSSER JASMUNDER BODDEN BANZELVITZER BERG Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0802
euProtectedAreaCode.DEMV_PR_1_0803 GROSSER JASMUNDER BODDEN RALSWIEK Quick edit Deprecated - retired 2025-01-29 DEMV_PR_1_0803
euProtectedAreaCode.DEMV_PR_1_0804 GROSSER JASMUNDER BODDEN LIETZOW Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0804
euProtectedAreaCode.DEMV_PR_1_0808 WIEKER BODDEN DRANSKER BODDENSTRAND Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0808
euProtectedAreaCode.DEMV_PR_1_0809 OSTSEE GOOS-LANCKEN Quick edit Deprecated - retired 2025-01-29 DEMV_PR_1_0809
euProtectedAreaCode.DEMV_PR_1_0816 OSTSEE GLOWE Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0816
euProtectedAreaCode.DEMV_PR_1_0818 OSTSEE ROSENGARTEN Quick edit Deprecated - retired 2025-01-29 DEMV_PR_1_0818
euProtectedAreaCode.DEMV_PR_1_0819 OSTSEE MUKRAN Quick edit Deprecated - retired 2025-01-29 DEMV_PR_1_0819
euProtectedAreaCode.DEMV_PR_1_0820 OSTSEE WAASE FOCKERSTROM Quick edit Deprecated - retired 2025-01-29 DEMV_PR_1_0820
euProtectedAreaCode.DEMV_PR_1_0821 OSTSEE SASSNITZ STRANDPROMENADE Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0821
euProtectedAreaCode.DEMV_PR_1_0831 GREIFSWALDER BODDEN ELDENA STRANDBAD Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0831
euProtectedAreaCode.DEMV_PR_1_0832 GREIFSWALDER BODDEN INSEL RIEMS Quick edit Deprecated - retired 2025-01-29 DEMV_PR_1_0832
euProtectedAreaCode.DEMV_PR_1_0836 STRELASUND STRANDBAD STRALSUND Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0836
euProtectedAreaCode.DEMV_PR_1_0837 OSTSEE STRELASUND FREIBAD Quick edit Deprecated - retired 2025-01-29 DEMV_PR_1_0837
euProtectedAreaCode.DEMV_PR_1_0838 STRELASUND DEVIN Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0838
euProtectedAreaCode.DEMV_PR_1_0842 STRELASUND KRAMERHOF PAROW Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0842
euProtectedAreaCode.DEMV_PR_1_0870 WIEKER BODDEN AOK KLINIK RUEGEN Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0870
euProtectedAreaCode.DEMV_PR_1_0871 WIEKER BODDEN WIEK HAFEN BOOTSWERFT Quick edit Valid - stable 2025-01-29 DEMV_PR_1_0871
euProtectedAreaCode.DEMV_PR_2_0001 SCHWERINER SEE ZIPPENDORFER STRAND Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0001
euProtectedAreaCode.DEMV_PR_2_0004 SCHWERINER SEE AM REPPIN Quick edit Valid - stable 2025-01-29 DEMV_PR_2_0004
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?