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 221 to 240.First89101112131415Last
Id Label Status Status Modified Notation
804 Range for pollutant 709 for var in pg.m-3 specific to GB Quick edit Valid 2018-08-13 804
805 Range for pollutant 712 for var in ng.m-3 specific to GB Quick edit Valid 2018-08-13 805
806 Range for pollutant 715 for var in ng.m-3 specific to GB Quick edit Valid 2018-08-13 806
807 Range for pollutant 1629 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 807
808 Range for pollutant 1668 for hour in ug.m-3 specific to GB Quick edit Valid 2018-08-13 808
809 Range for pollutant 1771 for week in ug.m-3 specific to GB Quick edit Valid 2018-08-13 809
810 Range for pollutant 1772 for week in ug.m-3 specific to GB Quick edit Valid 2018-08-13 810
811 Range for pollutant 4330 for var in pg.m-3 specific to GB Quick edit Valid 2018-08-13 811
812 Range for pollutant 4336 for var in pg.m-3 specific to GB Quick edit Valid 2018-08-13 812
813 Range for pollutant 4339 for var in pg.m-3 specific to GB Quick edit Valid 2018-08-13 813
814 Range for pollutant 4341 for var in pg.m-3 specific to GB Quick edit Valid 2018-08-13 814
815 Range for pollutant 4406 for var in ng.m-3 specific to GB Quick edit Valid 2018-08-13 815
816 Range for pollutant 4813 for var in ng.m-3 specific to GB Quick edit Valid 2018-08-13 816
817 Range for pollutant 4813 for year in ng.m-3 specific to GB Quick edit Valid 2018-08-13 817
818 Range for pollutant 5029 for 3month in ng.m-3 specific to GB Quick edit Valid 2018-08-13 818
819 Range for pollutant 5029 for var in ng.m-3 specific to GB Quick edit Valid 2018-08-13 819
820 Range for pollutant 5419 for year in ng.m-3 specific to GB Quick edit Valid 2018-08-13 820
821 Range for pollutant 5610 for 3month in ng.m-3 specific to GB Quick edit Valid 2018-08-13 821
822 Range for pollutant 5610 for var in ng.m-3 specific to GB Quick edit Valid 2018-08-13 822
823 Range for pollutant 5617 for year in ng.m-3 specific to GB Quick edit Valid 2018-08-13 823
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?