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

610 concepts found, displaying 181 to 200.First678910111213Last
Id Label Status Status Modified Notation
764 Range for pollutant 428 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 764
765 Range for pollutant 430 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 765
766 Range for pollutant 431 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 766
767 Range for pollutant 432 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 767
768 Range for pollutant 435 for var in ng.m-3 specific to GB Quick edit Valid 2018-08-13 768
769 Range for pollutant 441 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 769
770 Range for pollutant 443 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 770
771 Range for pollutant 447 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 771
772 Range for pollutant 449 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 772
773 Range for pollutant 450 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 773
774 Range for pollutant 451 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 774
775 Range for pollutant 464 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 775
776 Range for pollutant 475 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 776
777 Range for pollutant 482 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 777
778 Range for pollutant 486 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 778
779 Range for pollutant 503 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 779
780 Range for pollutant 505 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 780
781 Range for pollutant 606 for var in ng.m-3 specific to GB Quick edit Valid 2018-08-13 781
782 Range for pollutant 609 for var in ng.m-3 specific to GB Quick edit Valid 2018-08-13 782
783 Range for pollutant 622 for var in ng.m-3 specific to GB Quick edit Valid 2018-08-13 783
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?