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 541 to 560.First2324252627282930Last
Id Label Status Status Modified Notation
541 Range for pollutant 6012 for week in ug.m-3 Quick edit Valid 2016-11-17 541
542 Range for pollutant 6013 for day in ug.m-3 Quick edit Valid 2016-11-17 542
543 Range for pollutant 6013 for hour in ug.m-3 Quick edit Valid 2016-11-17 543
544 Range for pollutant 6013 for var in ug.m-3 Quick edit Valid 2016-11-17 544
545 Range for pollutant 6013 for week in ug.m-3 Quick edit Valid 2016-11-17 545
546 Range for pollutant 6015 for day in ng.m-3 Quick edit Valid 2016-11-17 546
547 Range for pollutant 6015 for month in ng.m-3 Quick edit Valid 2016-11-17 547
548 Range for pollutant 6015 for var in ng.m-3 Quick edit Valid 2016-11-17 548
549 Range for pollutant 6015 for year in ng.m-3 Quick edit Valid 2016-11-17 549
550 Range for pollutant 6380 for day in ng.m-3 Quick edit Valid 2016-11-17 550
551 Range for pollutant 7012 for month in ug.m-2.day-1 Quick edit Valid 2016-11-17 551
552 Range for pollutant 7012 for week in ug.m-2.day-1 Quick edit Valid 2016-11-17 552
553 Range for pollutant 7012 for year in ug.m-2.day-1 Quick edit Valid 2016-11-17 553
554 Range for pollutant 7013 for month in ug.m-2.day-1 Quick edit Valid 2016-11-17 554
555 Range for pollutant 7013 for var in ug.m-2.day-1 Quick edit Valid 2016-11-17 555
556 Range for pollutant 7013 for year in ug.m-2.day-1 Quick edit Valid 2016-11-17 556
557 Range for pollutant 7014 for day in ug.m-2.day-1 Quick edit Valid 2016-11-17 557
558 Range for pollutant 7014 for month in ug.m-2.day-1 Quick edit Valid 2016-11-17 558
559 Range for pollutant 7014 for var in ug.m-2.day-1 Quick edit Valid 2016-11-17 559
560 Range for pollutant 7014 for week in ug.m-2.day-1 Quick edit Valid 2016-11-17 560
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?