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,581 to 2,600.First126127128129130131132133Last
Id Label Status Status Modified Notation
DE2136401 Schlemminer Wälder Quick edit Valid 2018-01-19 DE2136401
DE2137302 Schlemminer Wälder und Kleingewässerlandschaft Quick edit Valid 2018-01-19 DE2137302
DE2137401 Warnowtal, Sternberger Seen und untere Mildenitz Quick edit Valid 2018-01-19 DE2137401
DE2138302 Warnowtal mit kleinen Zuflüssen Quick edit Valid 2018-01-19 DE2138302
DE2139301 Bockhorst Quick edit Valid 2018-01-19 DE2139301
DE2141301 Kleingewässerlandschaft nördlich von Jördenstorf Quick edit Valid 2018-01-19 DE2141301
DE2142301 Wald- und Kleingewässerlandschaft südöstlich von Altkalen Quick edit Valid 2018-01-19 DE2142301
DE2142302 Eichenreihe bei Groß Markow Quick edit Valid 2018-01-19 DE2142302
DE2142401 Kämmericher Senke Quick edit Valid 2018-01-19 DE2142401
DE2147401 Peenetallandschaft Quick edit Valid 2018-01-19 DE2147401
DE2210401 Niedersächsisches Wattenmeer und angrenzendes Küstenmeer Quick edit Valid 2018-01-19 DE2210401
DE2213401 Wangerland Quick edit Valid 2018-01-19 DE2213401
DE2218301 Ahlen-Falkenberger Moor, Seen bei Bederkesa Quick edit Valid 2018-01-19 DE2218301
DE2218302 Aßbütteler und Herrschaftliches Moor Quick edit Valid 2018-01-19 DE2218302
DE2220301 Balksee und Randmoore, Nordahner Holz Quick edit Valid 2018-01-19 DE2220301
DE2221301 Oederquarter Moor Quick edit Valid 2018-01-19 DE2221301
DE2222321 Wetternsystem in der Kollmarer Marsch Quick edit Valid 2018-01-19 DE2222321
DE2224305 Staatsforst Rantzau östlich Tornesch Quick edit Valid 2018-01-19 DE2224305
DE2224306 Obere Krückau Quick edit Valid 2018-01-19 DE2224306
DE2224391 Himmelmoor, Kummerfelder Gehege und angrenzende Flächen Quick edit Valid 2018-01-19 DE2224391
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?