Heavy metals present in the sample and their concentrations.
URI: MIXS:0000652
Alias: heavy_metals
Inheritance
Applicable Classes
Name |
Description |
Modifies Slot |
SoilInterface |
soil dh_interface |
no |
Properties
Aliases
- extreme_unusual_properties/heavy metals
Examples
Value |
mercury;0.09 ug/g |
mercury;0.09 ug/g |
- For multiple heavy metals and concentrations, separate by ;
TODOs
- Example & validation. Can we configure things so that 27% & 27 % & 0.27 will validate?
- I think it's weird the way GSC writes the title. I recommend this change. Thoughts? I would argue this isn't an extreme unusual property. It's just a biogeochemical measurement.
Annotations
property |
value |
expected_value |
heavy metal name;measurement value unit |
preferred_unit |
microgram per gram |
occurrence |
m |
Schema Source
Mappings
Mapping Type |
Mapped Value |
self |
MIXS:0000652 |
native |
nmdc_sub_schema:heavy_metals |
LinkML Source
name: heavy_metals
annotations:
expected_value:
tag: expected_value
value: heavy metal name;measurement value unit
preferred_unit:
tag: preferred_unit
value: microgram per gram
occurrence:
tag: occurrence
value: m
description: Heavy metals present in the sample and their concentrations.
title: heavy metals/ extreme unusual properties
todos:
- Example & validation. Can we configure things so that 27% & 27 % & 0.27 will validate?
- I think it's weird the way GSC writes the title. I recommend this change. Thoughts?
I would argue this isn't an extreme unusual property. It's just a biogeochemical
measurement.
comments:
- For multiple heavy metals and concentrations, separate by ;
examples:
- value: mercury;0.09 ug/g
- value: mercury;0.09 ug/g|chromium;0.03 ug/g
from_schema: https://example.com/nmdc_submission_schema
aliases:
- extreme_unusual_properties/heavy metals
rank: 17
is_a: core field
string_serialization: '{text};{float} {unit}'
slot_uri: MIXS:0000652
alias: heavy_metals
domain_of:
- SoilInterface
slot_group: mixs_section
range: string
multivalued: false