You are here:
Eionet
Data Dictionary
Edit vocabulary

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,461 to 3,480.First170171172173174175176177Last
Id Label Status Status Modified Notation
DE3426301 Brand Quick edit Valid 2018-01-19 DE3426301
DE3427301 Bohlenbruch Quick edit Valid 2018-01-19 DE3427301
DE3427331 Erse Quick edit Valid 2018-01-19 DE3427331
DE3429401 Großes Moor bei Gifhorn Quick edit Valid 2018-01-19 DE3429401
DE3430301 Vogelmoor Quick edit Valid 2018-01-19 DE3430301
DE3431302 Obere Ohre Quick edit Valid 2018-01-19 DE3431302
DE3431331 Drömling Quick edit Valid 2018-01-19 DE3431331
DE3431401 Drömling Quick edit Valid 2018-01-19 DE3431401
DE3432401 Feldflur bei Kusey Quick edit Valid 2018-01-19 DE3432401
DE3433301 Jeggauer Moor Quick edit Valid 2018-01-19 DE3433301
DE3434301 Jävenitzer Moor Quick edit Valid 2018-01-19 DE3434301
DE3434302 Kellerberge nordöstlich Gardelegen Quick edit Valid 2018-01-19 DE3434302
DE3434303 Brauereikeller Gardelegen Quick edit Valid 2018-01-19 DE3434303
DE3435301 Mooswiese Hottendorf östlich Gardelegen Quick edit Valid 2018-01-19 DE3435301
DE3435302 Spitzberg südwestlich Klinke Quick edit Valid 2018-01-19 DE3435302
DE3436301 Fenn in Wittenmoor Quick edit Valid 2018-01-19 DE3436301
DE3437302 Elbaue zwischen Derben und Schönhausen Quick edit Valid 2018-01-19 DE3437302
DE3437303 Stendaler Rohrwiesen Quick edit Valid 2018-01-19 DE3437303
DE3437401 Elbaue Jerichow Quick edit Valid 2018-01-19 DE3437401
DE3439302 Großes Fenn Quick edit Valid 2018-01-19 DE3439302
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?