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,131 concepts found, displaying 3,061 to 3,080.First150151152153154155156157Last
Id Label Status Status Modified Notation
DE2836302 Stavenower Wald Quick edit Valid 2018-01-19 DE2836302
DE2836303 Bootzer Torfloch Quick edit Valid 2018-01-19 DE2836303
DE2837301 Schlatbach Quick edit Valid 2018-01-19 DE2837301
DE2837302 Weinberge - Klüssenberge bei Perleberg Quick edit Valid 2018-01-19 DE2837302
DE2838301 Großer Horst Quick edit Valid 2018-01-19 DE2838301
DE2842301 Wummsee und Twernsee Quick edit Valid 2018-01-19 DE2842301
DE2842302 Buchheide Quick edit Valid 2018-01-19 DE2842302
DE2842303 Erweiterung Wumm- und Twernsee Quick edit Deprecated 2023-01-26 DE2842303
DE2842304 Uferbereiche Großer Wummsee, Twern- und Giesenschlagsee (MV) Quick edit Valid 2018-01-19 DE2842304
DE2843302 Forst Buberow Quick edit Valid 2018-01-19 DE2843302
DE2843303 Himmelreich Quick edit Valid 2018-01-19 DE2843303
DE2843304 Teufelsbruch (Wolfsbruch) Quick edit Valid 2018-01-19 DE2843304
DE2843305 Dollgowsee Quick edit Valid 2018-01-19 DE2843305
DE2843326 Großer Pätschsee bei Rheinsberg Quick edit Valid 2018-01-19 DE2843326
DE2843327 Rochowsee und Plötzensee Quick edit Deprecated 2023-01-26 DE2843327
DE2843401 Stechlin Quick edit Valid 2018-01-19 DE2843401
DE2844301 Stechlin Quick edit Valid 2018-01-19 DE2844301
DE2844302 Polzowtal Quick edit Valid 2018-01-19 DE2844302
DE2844303 Gramzow-Seen Quick edit Valid 2018-01-19 DE2844303
DE2844304 Globsower Buchheide Quick edit Valid 2018-01-19 DE2844304
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?