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

Prevent James A Lovell TRICARE facility drift #13706

Open swirtSJW opened 1 year ago

swirtSJW commented 1 year ago

User Story or Problem Statement

As a Lovell site maintainer I expect that any data that is changed by the nightly VAMC facility migration is propagated from the VA James A Lovell facility (vha_556 in Facility API) to the TRICARE James A Lovell facility (tricare_556) that is not in Facility API

As it is now, Changes to James A Lovell VA will track the facility API data, but James A Lovell TRICARE is not updated, and can become out of sync.

Acceptance Criteria

Implementation steps

This could be done as a post save hook, or it could be done with a post migration task that just syncs VA to TRICAE no matter if data changed or not.

Design principles

Veteran-centered

kmariepat-cityfriends commented 1 year ago

Next Steps: Is VAST the canonical information for the TRICARE half of Lovell, ask in Lovell office hours on 5/18

jilladams commented 1 year ago

Per Steve: there is an implementation difference between matching the data on migration, vs. on node save. Answers from office hours will determine best path forward, in order to finalize plan and estimate.

omahane commented 1 year ago

Decisions regarding this and #13707 should result in documentation changes in Github and the Knowledge Base.

kmariepat-cityfriends commented 1 year ago

the information in VAST to their knowledge is the canonical information for the TRICARE half of Lovell