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,801 to 2,820.First137138139140141142143144Last
Id Label Status Status Modified Notation
DE2516331 Nebenarme der Weser mit Strohauser Plate und Juliusplate Quick edit Valid 2018-01-19 DE2516331
DE2517301 Placken-, Königs- und Stoteler Moor Quick edit Valid 2018-01-19 DE2517301
DE2517331 Teichfledermaus-Gewässer im Raum Bremerhaven/Bremen Quick edit Valid 2018-01-19 DE2517331
DE2518301 Silbersee, Laaschmoor, Bülter See, Bülter Moor Quick edit Valid 2018-01-19 DE2518301
DE2518331 Niederungen von Billerbeck und Oldendorfer Bach Quick edit Valid 2018-01-19 DE2518331
DE2519301 Wollingster See mit Randmoor Quick edit Valid 2018-01-19 DE2519301
DE2519331 Malse Quick edit Valid 2018-01-19 DE2519331
DE2519332 Franzhorn Quick edit Valid 2018-01-19 DE2519332
DE2520331 Oste mit Nebenbächen Quick edit Valid 2018-01-19 DE2520331
DE2520332 Spreckenser Moor Quick edit Valid 2018-01-19 DE2520332
DE2522301 Auetal und Nebentäler Quick edit Valid 2018-01-19 DE2522301
DE2522302 Braken Quick edit Valid 2018-01-19 DE2522302
DE2522331 Hahnenhorst Quick edit Valid 2018-01-19 DE2522331
DE2523331 Neuklosterholz Quick edit Valid 2018-01-19 DE2523331
DE2524331 Este, Bötersheimer Heide, Glüsinger Bruch und Osterbruch Quick edit Valid 2018-01-19 DE2524331
DE2524332 Este-Unterlauf Quick edit Valid 2018-01-19 DE2524332
DE2524401 Moore bei Buxtehude Quick edit Valid 2018-01-19 DE2524401
DE2524402 Moorgürtel Quick edit Valid 2018-01-19 DE2524402
DE2525301 Fischbeker Heide Quick edit Valid 2018-01-19 DE2525301
DE2525302 Buchenwälder in Rosengarten Quick edit Valid 2018-01-19 DE2525302
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?