VAMC Facility duplicate record: San Antonio-Pecan Valley VA Clinic

JayDarnell commented 1 year ago

Relates to #12647 See details initially outlined in #12576 There are currently two facility records in VAST for this clinic.

Intake

[ ] What triggered this runbook? (Flag in CMS, Help desk ticket, Product team, VHA Digital Media) Trigger:
[ ] Link to associated help desk ticket (if applicable) Help desk ticket:
[ ] Name of submitter (if applicable) Submitter:
[ ] Link to facility in production: Facility link:

Steps before proceeding

[ ] Check with Facilities team Product Owner to get approval of section change.
[ ] Check with VHA Digital Media.

VAMC facility section change (and duplicate VAST records)

A section change is typically represented by two facility records in VAST for a single physical location. In most cases the only difference between the two records are the Facility API ID values for each facility.

Duplicate records can also show up in VAST as the result of a facility name change if VAST opted to create a new record with the new name (with a new Facility API ID) instead of simply updating the name field for the existing facility record.

In either instance we have two VAST records representing the same physical location and we need to make changes in the CMS so VAST data for the NEW VAST entry properly maps to our original CMS facility. We do this to preserve revision log information and other history stored in the CMS.

CMS help desk steps

[ ] 1. Submit a redirect request from the original URL for the facility to the new URL for the facility.

(These are usually released Wednesday afternoons so you should coordinate the remaining items below around that timeframe) #### CMS engineer steps (the new facility) - [x] 2. Change the Facility Locator API ID on the new facility (vha_671GU) to the Facility Locator API ID for the old one (vha_671GK03). - [x] 3. Change the section on the new facility to the old one - [x] 4. Change the VAMC system on the new facility to the old one - [x] 5. Update the Menu link (Parent link) on the new facility to the old system (unable to delete it) - [x] 6. Check the box under URL alias to **Generate automatic URL alias** - [x] 7. Archive the facility with a good log message - [x] 8. Manually disable the menu link for this item directly in the system menu #### CMS engineer steps (the original facility) - [x] 9. Change the Facility Locator API ID on the old facility to the Facility Locator API ID for new one - [x] 10. Change the section on the old facility to the new one - [x] 11. Change the VAMC system on the old facility to the new one - [x] 12. Update the Menu link (Parent link) on the old facility to the new system - [x] 13. Check the box under URL alias to **Generate automatic URL alias** - [x] 14. Publish changes with good log message - [x] 15. Manually move the menu link for this item into alphabetical order in locations section of the menu for its new system #### CMS engineer steps (bulk edit) Update related content (VAMC Facility Health Services, VAMC Non-clinical Services, Events, Stories, etc) - [x] 16. Bulk edit the VAMC Facility Health Services for the original Facility (update the section to the new section) - [x] 17. Manually edit each VAMC Facility Health Service (updating the VAMC system health service to use the new system) - [x] 18. Bulk edit the VAMC Facility Health Services to **Update URL alias** - [x] 19. Bulk edit the VAMC Facility Health services to **Resave content** (now the urls will be correct) #### CMS engineer (create sript to be run against the production DB) This script will need to be run against the production database by a member of the platform team and should accomplish the following goals: - [x] Remove the migrate_map entry for the new facility - [x] Update the migrate_map entry for the old facility, updating the facility locator api id to the new one (sql command in drush) **Paste the script to be run here** #### Example script ``` drush sql:query "DELETE FROM migrate_map_va_node_health_care_local_facility WHERE sourceid1 = 'vha_671GU'" drush sql:query "UPDATE migrate_map_va_node_health_care_local_facility SET sourceid1 = 'vha_671GU' WHERE sourceid1 = 'vha_671GK03'" ``` #### CMS engineer (update lighthouse) In [Lighthouse Facilties](https://github.com/department-of-veterans-affairs/lighthouse-facilities) - [x] 20. CMS engineer updates the [CSV in Lighthouse](https://github.com/department-of-veterans-affairs/lighthouse-facilities/blob/master/facilities/src/main/resources/websites.csv) with the changed URL, creating a PR, tagging the Lighthouse team and linking to it in Slack with an @mention to a Lighthouse team member. The PR is [lighthouse-facilities/pull/428](https://github.com/department-of-veterans-affairs/lighthouse-facilities/pull/428) #### CMS Help desk (wrap up) - [ ] Help desk notifies editor and any other stakeholders. ### Team Please check the team(s) that will do this work. - [ ] `CMS Team` - [ ] `Public Websites` - [x] `Facilities` - [x] `User support`

stefaniefgray commented 1 year ago

Tickets: https://va-gov.atlassian.net/browse/VAHELP-5506 https://va-gov.atlassian.net/browse/VAHELP-5339

omahane commented 1 year ago

@stefaniefgray @TroyA6 The duplicate is archived. The changes have been made to https://prod.cms.va.gov/south-texas-health-care/locations/san-antonio-pecan-valley-va-clinic so that it syncs with Lighthouse.

omahane commented 1 year ago

@stefaniefgray @TroyA6 Can you confirm with editors and any other stakeholders that this work is complete?

omahane commented 1 year ago

@stefaniefgray @TroyA6 The canonical link and redirect has been made. I'll let you know when I see the va.gov change live.

stefaniefgray commented 1 year ago

@omahane Sounds good!

omahane commented 1 year ago

@TroyA6 The full facility page is now being returned in the Facility Locator.

TroyA6 commented 1 year ago

@stefaniefgray @JayDarnell @omahane @kmariepat-cityfriends - I have reviewed the requested changes in production; everything seems to be correct - The displayed address is correct, the Facility ID is correct within CMS, the production site and links TO the site all appear to be working correctly. It is my opinion the editor can now be contacted, and ticket closed.

TroyA6 commented 1 year ago

@stefaniefgray @omahane @kmariepat-cityfriends - Editor has been notified; I will close this issue, but please let me know if I am in error.

stefaniefgray commented 1 year ago

@TroyA6 Please add Jira link where editor was notified so that I can link it to the original ticket -- thank you!

stefaniefgray commented 1 year ago

@TroyA6 ^^

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