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
maximumValue Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
17 Nov 2016
minimumValue Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
17 Nov 2016
primaryObservationTime Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
17 Nov 2016
recommendedUnit Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
25 Sep 2013
relatedPollutant Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
15 Apr 2014

Add new data elements

Mandatory
Mandatory
Optional
Optional (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

585 concepts found, displaying 341 to 360.First1415161718192021Last
Id Label Status Status Modified Notation
341 Range for pollutant 1047 for var in ug.m-3 Quick edit Valid 2016-11-17 341
342 Range for pollutant 1047 for week in ug.m-3 Quick edit Valid 2016-11-17 342
343 Range for pollutant 1047 for year in ug.m-3 Quick edit Valid 2016-11-17 343
344 Range for pollutant 1063 for day in ng.m-3 Quick edit Valid 2016-11-17 344
345 Range for pollutant 1629 for day in ug.m-3 Quick edit Valid 2016-11-17 345
346 Range for pollutant 1629 for hour in ug.m-3 Quick edit Valid 2016-11-17 346
347 Range for pollutant 1629 for var in ug.m-3 Quick edit Valid 2016-11-17 347
348 Range for pollutant 1629 for week in ug.m-3 Quick edit Valid 2016-11-17 348
349 Range for pollutant 1629 for year in ug.m-3 Quick edit Valid 2016-11-17 349
350 Range for pollutant 1631 for day in ug.m-3 Quick edit Valid 2016-11-17 350
351 Range for pollutant 1631 for hour in ug.m-3 Quick edit Valid 2016-11-17 351
352 Range for pollutant 1631 for var in ug.m-3 Quick edit Valid 2016-11-17 352
353 Range for pollutant 1631 for week in ug.m-3 Quick edit Valid 2016-11-17 353
354 Range for pollutant 1631 for year in ug.m-3 Quick edit Valid 2016-11-17 354
355 Range for pollutant 1657 for day in ug.m-3 Quick edit Valid 2016-11-17 355
356 Range for pollutant 1657 for hour in ug.m-3 Quick edit Valid 2016-11-17 356
357 Range for pollutant 1657 for var in ug.m-3 Quick edit Valid 2016-11-17 357
358 Range for pollutant 1657 for week in ug.m-3 Quick edit Valid 2016-11-17 358
359 Range for pollutant 1657 for year in ug.m-3 Quick edit Valid 2016-11-17 359
360 Range for pollutant 1659 for day in ug.m-3 Quick edit Valid 2016-11-17 360
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?