Slot: history/fire (fire)

Historical and/or physical evidence of fire

Inheritance

core_field
- fire

Applicable Classes

Name	Description	Modifies Slot
SedimentInterface	sediment dh_interface	no
SoilInterface	soil dh_interface	no

Properties

Range: String
Regex pattern: ^[12]\d{3}(?:(?:-(?:0[1-9]|1[0-2]))(?:-(?:0[1-9]|[12]\d|3[01]))?)?(\s+to\s+[12]\d{3}(?:(?:-(?:0[1-9]|1[0-2]))(?:-(?:0[1-9]|[12]\d|3[01]))?)?)?$

Aliases

history/fire

Examples

Value
1871-10-10
1871-10-01 to 1871-10-31

Comments

Provide the date the fire occurred. If extended burning occurred provide the date range.

TODOs

is "to" acceptable? Is there a better way to request that be written?

Identifier and Mapping Information

Annotations

property	value
expected_value	date string

Schema Source

from schema: https://example.com/nmdc_submission_schema

Mappings

Mapping Type	Mapped Value
self	MIXS:0001086
native	nmdc_sub_schema:fire

LinkML Source

name: fire
annotations:
  expected_value:
    tag: expected_value
    value: date string
description: Historical and/or physical evidence of fire
title: history/fire
todos:
- is "to" acceptable? Is there a better way to request that be written?
comments:
- Provide the date the fire occurred. If extended burning occurred provide the date
  range.
examples:
- value: '1871-10-10'
- value: 1871-10-01 to 1871-10-31
from_schema: https://example.com/nmdc_submission_schema
aliases:
- history/fire
rank: 15
is_a: core field
slot_uri: MIXS:0001086
alias: fire
domain_of:
- SedimentInterface
- SoilInterface
slot_group: mixs_section
range: string
multivalued: false
pattern: ^[12]\d{3}(?:(?:-(?:0[1-9]|1[0-2]))(?:-(?:0[1-9]|[12]\d|3[01]))?)?(\s+to\s+[12]\d{3}(?:(?:-(?:0[1-9]|1[0-2]))(?:-(?:0[1-9]|[12]\d|3[01]))?)?)?$