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 2,941 to 2,960.First144145146147148149150151Last
Id Label Status Status Modified Notation
DE2713331 Wittenheim und Silstro Quick edit Valid 2018-01-19 DE2713331
DE2713332 Garnholt Quick edit Valid 2018-01-19 DE2713332
DE2714331 Mansholter Holz, Schippstroht Quick edit Valid 2018-01-19 DE2714331
DE2714332 Elmendorfer Holz Quick edit Valid 2018-01-19 DE2714332
DE2715301 Ipweger Moor, Gellener Torfmöörte Quick edit Valid 2018-01-19 DE2715301
DE2715331 Eichenbruch, Ellernbusch Quick edit Valid 2018-01-19 DE2715331
DE2715332 Funchsbüsche, Ipweger Büsche Quick edit Valid 2018-01-19 DE2715332
DE2716331 Mittlere und Untere Hunte (mit Barneführer Holz und Schreensmoor) Quick edit Valid 2018-01-19 DE2716331
DE2717301 Heide und Heideweiher auf der Rekumer Geest Quick edit Valid 2018-01-19 DE2717301
DE2717331 Garlstedter Moor und Heidhofer Teiche Quick edit Valid 2018-01-19 DE2717331
DE2717332 Brundorfer Moor Quick edit Valid 2018-01-19 DE2717332
DE2718301 Reithbruch Quick edit Valid 2018-01-19 DE2718301
DE2718331 Schönebecker Aue Quick edit Valid 2018-01-19 DE2718331
DE2718332 Untere Wümmeniederung, untere Hammeniederung mit Teufelsmoor Quick edit Valid 2018-01-19 DE2718332
DE2719401 Hammeniederung Quick edit Valid 2018-01-19 DE2719401
DE2720331 Hepstedter Büsche Quick edit Valid 2018-01-19 DE2720331
DE2721301 Bullensee, Hemelsmoor Quick edit Valid 2018-01-19 DE2721301
DE2721331 Borstgrasrasen bei Badenstedt Quick edit Valid 2018-01-19 DE2721331
DE2722331 Sotheler Moor Quick edit Valid 2018-01-19 DE2722331
DE2723301 Großes Moor bei Wistedt Quick edit Valid 2018-01-19 DE2723301
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?