ARCIM uses the Winlink generated CSV as its database.
When you do the "DYFI report" in PAT, the data is embedded in the body of the message. Tools for auto-extraction expect there to be a text attachment to the message, not just in the body.
Since the DYFI report isn't an attachment, it fails to process the data, leading to failed/incomplete checkins.
Way to reproduce:
Action -> Compose -> Template -> USGS - > USGS-DYFI -> (fill out form with info) -> submit -> Continue -> observe that it's just text in the body, and not an attachment.
This bug arose during the "Great Shakeout" event:
ARCIM uses the Winlink generated CSV as its database.
When you do the "DYFI report" in PAT, the data is embedded in the body of the message. Tools for auto-extraction expect there to be a text attachment to the message, not just in the body.
Since the DYFI report isn't an attachment, it fails to process the data, leading to failed/incomplete checkins.
Way to reproduce: Action -> Compose -> Template -> USGS - > USGS-DYFI -> (fill out form with info) -> submit -> Continue -> observe that it's just text in the body, and not an attachment.