Discovery: Derive insights into how FOM-building process impacts our strategy

[wesrowe]

Description

Review documentation of FOM data entry/editing process, meet with Janet, and condense insights to how the existing FOM process and system can help us reach MVP.

Acceptance Criteria

• [x] Review documents
• [x] Have call with Janet (2/11)
• [x] Document insights re FOM process in WIP FOM Gdoc
• [x] Review FOM levels 2-4 for presence of Activities and Overview content (expecting Mission only at Level 2) – currently blocked by lack of level data in CSV (Wes will try to use Airtable as an alternative to spreadsheets if time allows)
• [x] Meet internally to determine impact of new learnings. UPDATE: we discussed internally in scrum, 2/15/22, that we will de-prioritize development of an automated CSV ingest/update system due to the fact that the FOM database only gets updated officially once per year. For MVP we will assume some manual steps in updating our Directory data.
• [x] Impact of FOM data update processes is documented in Mural

CMS Team

Please leave only the team that will do this work selected. If you're not sure, it's fine to leave both selected.

• [ ] Platform CMS Team
• [ ] Sitewide CMS Team
  • [ ] ⭐️ Content ops
  • [ ] ⭐️ CMS experience
  • [x] ⭐️ Offices
  • [ ] ⭐️ Product support
  • [ ] ⭐️ User support

[wesrowe]

Just realized this issue didn't have the sprint labeled

[wesrowe]

This ticket is ready to close, as one AC is blocked indefinitely by lack of a Level column in the CSV. I'm leaving it open in the hope that I'll find time to try getting the info I need by importing the csv to AirTable and trying out some of its relational features.

[wesrowe]

NOTE: This issue is a sprint goal for sprint 52, but moving it to the Review column cleared the pin.

[wesrowe]

Linked to Mural of our insights. Closing issue.