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,510 concepts found, displaying 3,481 to 3,500.First171172173174175176177178Last
Id Label Status Status Modified Notation
DE3439303 Milower Berg Quick edit Valid 2018-01-19 DE3439303
DE3440301 Pritzerber Laake Quick edit Valid 2018-01-19 DE3440301
DE3440304 Gräninger See Quick edit Valid 2018-01-19 DE3440304
DE3441301 Weißes Fenn und Dünenheide Quick edit Valid 2018-01-19 DE3441301
DE3442302 Bagower Mühlenberg Quick edit Valid 2018-01-19 DE3442302
DE3442303 Bagower Bruch Quick edit Valid 2018-01-19 DE3442303
DE3442304 Beetzsee-Rinne und Niederungen Quick edit Valid 2018-01-19 DE3442304
DE3442305 Fledermausquartier in Klein Behnitz (Wohnhaus) Quick edit Valid 2018-01-19 DE3442305
DE3443301 Heimsche Heide Ergänzung Quick edit Valid 2018-01-19 DE3443301
DE3444303 Döberitzer Heide Quick edit Valid 2018-01-19 DE3444303
DE3444304 Heimsche Heide Quick edit Valid 2018-01-19 DE3444304
DE3444305 Rhinslake bei Rohrbeck Quick edit Valid 2018-01-19 DE3444305
DE3444306 Falkenseer Kuhlaake Quick edit Valid 2018-01-19 DE3444306
DE3444307 Bredower Forst Quick edit Valid 2018-01-19 DE3444307
DE3444308 Fort Hahneberg Quick edit Valid 2018-01-19 DE3444308
DE3444401 Döberitzer Heide Quick edit Valid 2018-01-19 DE3444401
DE3445301 Spandauer Forst Quick edit Valid 2018-01-19 DE3445301
DE3445302 Zitadelle Spandau Quick edit Valid 2018-01-19 DE3445302
DE3445303 Wasserwerk Tegel Quick edit Valid 2018-01-19 DE3445303
DE3445304 Baumberge Quick edit Valid 2018-01-19 DE3445304
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?