[Forecasted Pipeline] Update PublishGrantEvents lambda

[jeffsmohan]

Blocked by

• 874

Blocks

N/A

Why is this issue important?

We want forecasted grants available in our dataset (alongside active grants) so we can integrate them into the product for our users.

Current State

The PublishGrantEvents lambda function is responsible for taking new and updated grants in our DynamoDB and publishing those updates as events for GOST to consume and store in our postgres database. However, this lambda specifically handles grant fields but not forecasted grant fields.

Expected State

The lambda should add additional logic in mapper.go to handle the new forecasted specific fields (see field reference here, as well as the target schema documentation in openapi/openapi.yaml to be implemented in https://github.com/usdigitalresponse/grants-ingest/issues/874) like EstimatedAwardDate. It should also add a denormalized IsForecasted boolean field.

Implementation plan

Should be gated behind the is_forecasted_grants_enabled flag.

Exact implementation TBD

WIP Notes

New struct fields and mapping behaviors for data derived from OpportunityForecastDetail_1_0 records:

• Grant struct:
  • FiscalYear, mapped from FiscalYear
• GrantorContact struct:
  • Name, mapped from GrantorContactName
  • Phone, mapped from GrantorContactPhoneNumber
• OpportunityMilestones struct:
  • AwardDate, mapped from EstimatedAwardDate
  • ProjectStartDate, mapped from EstimatedProjectStartDate
  • ForecastCreationDate, mapped from PostDate

[TylerHendrickson]

Sprinkling some documentation assets around:

• Federal Grants data field mappings spreadsheet
• LucidChart diagram (companion to the above) collaboration
  • View-only diagram published 2024-07-29