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 301 to 320.First1213141516171819Last
Id Label Status Status Modified Notation
301 Range for pollutant 709 for var in pg.m-3 Quick edit Valid 2016-11-17 301
302 Range for pollutant 712 for day in ng.m-3 Quick edit Valid 2016-11-17 302
303 Range for pollutant 712 for var in ng.m-3 Quick edit Valid 2016-11-17 303
304 Range for pollutant 712 for year in ng.m-3 Quick edit Valid 2016-11-17 304
305 Range for pollutant 714 for month in ug.m-2.day-1 Quick edit Valid 2016-11-17 305
306 Range for pollutant 715 for day in ng.m-3 Quick edit Valid 2016-11-17 306
307 Range for pollutant 715 for month in ng.m-3 Quick edit Valid 2016-11-17 307
308 Range for pollutant 715 for var in ng.m-3 Quick edit Valid 2016-11-17 308
309 Range for pollutant 715 for year in ng.m-3 Quick edit Valid 2016-11-17 309
310 Range for pollutant 717 for month in ug.m-2.day-1 Quick edit Valid 2016-11-17 310
311 Range for pollutant 719 for day in mgS.m-1 Quick edit Valid 2016-11-17 311
312 Range for pollutant 728 for var in ug.l-1 Quick edit Valid 2016-11-17 312
313 Range for pollutant 728 for week in ug.l-1 Quick edit Valid 2016-11-17 313
314 Range for pollutant 753 for day in mm Quick edit Valid 2016-11-17 314
315 Range for pollutant 753 for var in mm Quick edit Valid 2016-11-17 315
316 Range for pollutant 753 for week in mm Quick edit Valid 2016-11-17 316
317 Range for pollutant 759 for var in ng.l-1 Quick edit Valid 2016-11-17 317
318 Range for pollutant 760 for day in ug.m-2.day-1 Quick edit Valid 2016-11-17 318
319 Range for pollutant 760 for month in ug.m-2.day-1 Quick edit Valid 2016-11-17 319
320 Range for pollutant 760 for var in ug.m-2.day-1 Quick edit Valid 2016-11-17 320
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?