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
hasProtectionTarget Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
21 Jul 2014
mandatoryUnit Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
27 Jul 2020
measurementEquipment Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
21 Jul 2014
recommendedUnit Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
25 Sep 2013
skos:altLabel Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013
skos:relatedMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013
skos:scopeNote Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

662 concepts found, displaying 561 to 580.First2526272829303132Last
Id Label Status Status Modified Notation
6015 Benzo(a)pyrene (air+aerosol) Quick edit Valid 2013-09-20 BaP
6016 1-Hexene (air) Quick edit Valid 2016-03-29 C6H12
6017 Butyl acetate (air) Quick edit Valid 2020-03-27 C6H12O2
6023 Ultra Fine Particles (UFPs) with a lower limit of 3 nanometers and no restriction on the upper limit - recommended unit: particles.cm-3 Quick edit Valid 2025-05-26 UFPs >3nm
6024 Ultra Fine Particles (UFPs) with a lower limit of 4 nanometers and no restriction on the upper limit - recommended unit: particles.cm-3 Quick edit Valid 2025-05-26 UFPs >4nm
6027 Ultra Fine Particles (UFPs) with a lower limit of 7 nanometers and no restriction on the upper limit - recommended unit: particles.cm-3 Quick edit Valid 2025-05-26 UFPs >7nm
6380 Benzo(b,j,k)fluoranthene in PM10 (air+aerosol) Quick edit Valid 2013-09-20 Benzo(b,j,k)fluorantheneInPM1
6382 Benzo(k+j)fluoranthene in PM10 (air+aerosol) Quick edit Valid 2022-04-22 Benzo(k+j)fluoranthene
6400 Volatile PM10 Quick edit Valid 2015-08-11 VPM10
6401 Non-volatile PM10 Quick edit Valid 2015-08-11 NVPM10
6410 Volatile PM2.5 Quick edit Valid 2015-08-11 VPM2.5
6411 Non-volatile PM2.5 Quick edit Valid 2015-08-11 NVPM2.5
6420 Volatile PM1 Quick edit Valid 2015-08-11 VPM1
6421 Non-volatile PM1 Quick edit Valid 2015-08-11 NVPM1
7012 Lead (precip+dry_dep) Quick edit Valid 2013-09-20 Pb
7013 Mercury (precip+dry_dep) Quick edit Valid 2013-09-20 Hg
7014 Cadmium (precip+dry_dep) Quick edit Valid 2013-09-20 Cd
7015 Nickel (precip+dry_dep) Quick edit Valid 2013-09-20 Ni
7016 Chromium (precip+dry_dep) Quick edit Valid 2016-03-29 Cr
7018 Arsenic (precip+dry_dep) Quick edit Valid 2013-09-20 As
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?