Some GGIRCS md5 hash values and file path values are not being parsed for attachment records [7]

[dleard]

We were alerted to this by viewing the Report Attachments with download URL question in metabase. Some file paths are missing & for every record that is missing a file path the record is also missing an md5 hash.

We'll need to do some investigation on this bug (sounds like a possible parsing error in the GGIRCS schema where we are parsing this attachment data). Once a solution has been found & implemented, alert Robb in the metabase channel as this was affecting some of the results used in compliance work.

Probability: 5 - this is currently an active issue that affects a large set of live results.

Effect: 2 - It is affecting some results needed for compliance regarding verification statements and file paths, but has been flagged as a fairly low priority/impact bug.