search

department-of-veterans-affairs / va.gov-cms

Editor-centered management for Veteran-centered content.
https://prod.cms.va.gov
GNU General Public License v2.0
97 stars 69 forks source link

Flagged Facilities: Better monitoring for upstream data changes #4856

Open kevwalsh opened 3 years ago

kevwalsh commented 3 years ago

Background

Google doc from December 9 with user stories and some UI, implementation ideas, and architecture questions.

We pull facility data from Facility API We pull forms data from formsDB

We push that data back with changes and additional content.

This is documented here: https://github.com/department-of-veterans-affairs/va.gov-cms/blob/master/READMES/migrations-facility.md

and

https://github.com/department-of-veterans-affairs/va.gov-cms/blob/master/READMES/vamc-facilities.md

How can we improve the governance of each step in the process?

See #4369 for various concerns and a spike ticket. Other issues to follow.

Feature Branch MVP (MVP was merged 1/18/2022)

All PRs should be against https://github.com/department-of-veterans-affairs/va.gov-cms/tree/VACMS-4856-Flags-Feature-Branch

Post MVP

Document business process / runbooks

jilladams commented 2 years ago

FormsDB is mentioned here -- now that Find a form is a PW product, would be good to understand the state of this work, and how it affects Find a form outside the context of facilities, if it does. (cc @wesrowe )

wesrowe commented 2 years ago

@jilladams, good find – I've seen this demoed (in winter) for facility changes. I didn't know it monitors forms as well. Let's make sure we talk about it in the Forms overview meeting.