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
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014
skos:broadMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

28,131 concepts found, displaying 2,501 to 2,520.First122123124125126127128129Last
Id Label Status Status Modified Notation
DE2020301 Klev- und Donnlandschaft bei St. Michaelisdonn Quick edit Valid 2018-01-19 DE2020301
DE2021301 Kudensee Quick edit Valid 2018-01-19 DE2021301
DE2021401 NSG Kudensee Quick edit Valid 2018-01-19 DE2021401
DE2022302 Vaaler Moor und Herrenmoor Quick edit Valid 2018-01-19 DE2022302
DE2023303 Rantzau-Tal Quick edit Valid 2018-01-19 DE2023303
DE2024301 Heiden und Dünen bei Störkathen Quick edit Valid 2018-01-19 DE2024301
DE2024308 Mühlenbarbeker Au und angrenzendes Quellhangmoor Quick edit Valid 2018-01-19 DE2024308
DE2024391 Mittlere Stör, Bramau und Bünzau Quick edit Valid 2018-01-19 DE2024391
DE2024392 Moore der Breitenburger Niederung Quick edit Valid 2018-01-19 DE2024392
DE2025303 Hasenmoor Quick edit Valid 2018-01-19 DE2025303
DE2026303 Osterautal Quick edit Valid 2018-01-19 DE2026303
DE2026304 Barker Heide Quick edit Valid 2018-01-19 DE2026304
DE2026305 Altwaldbestände im Segeberger Forst Quick edit Valid 2018-01-19 DE2026305
DE2026307 Moorweiher im Segeberger Forst Quick edit Valid 2018-01-19 DE2026307
DE2026401 Barker und Wittenborner Heide Quick edit Valid 2018-01-19 DE2026401
DE2027301 NSG Ihlsee und Ihlwald Quick edit Valid 2018-01-19 DE2027301
DE2027302 Segeberger Kalkberghöhlen Quick edit Valid 2018-01-19 DE2027302
DE2028352 Wald bei Söhren Quick edit Valid 2018-01-19 DE2028352
DE2028359 Wald nördlich Steinbek Quick edit Valid 2018-01-19 DE2028359
DE2028401 Wardersee Quick edit Valid 2018-01-19 DE2028401
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?