VAMC Facility name change: Wenatchee VA Clinic -> Elwood “Bud” Link Department of Veterans Affairs Outpatient Clinic

jilladams commented 1 year ago

Redirect request: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/13829

Backstory:

This facility name change first came to us in May 2023 mistakenly applied to the Fort Belvoir VA Clinic in VA Washington DC instead of VA Spokane in Washington State. The Fort Belvoir VA Clinic's name has since been changed back.

On 5/31/23, the Facilities API had flagged that the 'Wenatchee VA Clinic' in VA Spokane had been renamed to the 'Elwood “Bud” Link Department of Veteran Affairs Outpatient Clinic'. This is correct!

Instead of opening a brand new ticket, I am re-opening this one since it's already associated with this name.

Intake

[x] What triggered this runbook? (Flag in CMS, Help desk ticket, Product team, VHA Digital Media) Trigger: Flagged content view
[x] Link to associated help desk ticket (if applicable) Help desk ticket: N/A
[x] Name of submitter (if applicable) Submitter: @jilladams
[x] If the submitter is an editor, send them links to any relevant KB articles for the VAMC product. Let them know that facility changes can take between 75 days and 4 months after submitting a request, according to VAST administrators. KB article: "How Do I Update My VAMC Facility's Basic Location Data?"
[x] Link to facility in production: Facility CMS link: https://prod.cms.va.gov/spokane-health-care/locations/wenatchee-va-clinic Facility API ID: vha_668GA

Acceptance criteria

VAMC Facility name change

CMS help desk steps

Note: If the help desk is waiting on information from the facility staff or editor, add the "Awaiting editor" flag to the facility with a log message that includes a link to this ticket. Remove the flag when the ticket is ready to be worked by the Facilities team. Be sure to preserve the current moderation state of the node when adding or removing the flag. What happens: The name change is made in VAST, that syncs to Lighthouse which syncs to Drupal.

[x] 1. Check that the title change in name field on the VAMC node has shown up in Drupal.
[x] 2. Create a URL change request, changing the entry from the old facility URL to the new facility URL. (Note: The URL change request ticket blocks the completion of this ticket.)

https://github.com/department-of-veterans-affairs/va.gov-cms/issues/13829

CMS Engineer steps

[ ] 3. Execute the steps of the URL change request ticket from step 2 above.

(Redirects deploy weekly on Wed. at 10am ET, or by requesting OOB deploy (of the revproxy job to prod) in #vfs-platform-support. Coordinate the following items below and canonical URL change after URL change ticket is merged, deployed, and verified in prod.)

Drupal Admin steps (CMS Engineer or Help desk)

Help desk will complete these steps or escalate to request help from CMS engineering.

[x] 4. Locate the newly renamed VAMC Facility (https://prod.cms.va.gov/admin/content/bulk) Search by new name
[x] 5. Updates URL alias for this facility
[x] 6. Resave this facility
[x] 7. Make bulk alias changes to facility service nodes. (https://prod.cms.va.gov/admin/content/bulk?type=health_care_local_health_service)
[x] 8. Bulk save fixed titles to facility service nodes. (https://prod.cms.va.gov/admin/content/bulk?type=health_care_local_health_service)
[x] 9. Update menu title for facility
[x] 10. May also need to directly edit the VAMC System menu to alpha sort the menu item after the title changes
[x] 11. Update Alt text for facility image, if relevant
[x] 12. Update Meta description (TBD: some backwards compatibility for SEM, by including something like ", formerly known as [previous name]".
[x] 13. Edit facility node and remove flag Changed name then save node (with moderation state = published)