[CONSIDER] Revisit logic governing "Other nearby VA locations" on VAMC pages

[mmiddaugh]

Issue Description

The locations listed under "Other nearby VA locations" on VAMC system level Locations pages are currently handled manually by editors which means they are inconsistent, at best. The process also is neither intuitive or in line with our modernization efforts. The editor is prompted to visit the facility's detail page via the Facility Locator to pull the facility ID. Facility Locator detail pages are redirected once a modernized page is published. Modernized pages exist for VA health facilities and Vet Centers (and will soon for VBA Regional offices).

We may want to handle this automagically, as we do on Vet Centers and Regional office pages.

We may want to take this opportunity to uses graphQL queries and liquid templates to display the new entity reference

Screenshot

Screenshot

Related

• 11829

• See #12004 for more details regarding the CMS changes this issue builds upon.
• Engineering notes: Liquid template: (content-build) src/site/layouts/locations_listing.drupal.liquid

Examples: By comparison, the Locations page for Washington DC health care includes only 4 Vet Centers (ranging from 1 - 13 miles away) despite the presence of

• at least one National Cemetery (the closest of which is 9.5 miles away)
• at least one Regional office (the closest of which is 2.8 miles away)

Greater Los Angeles health care also lists only Vet Centers (8) despite the presence of a National cemetery and a Regional Office within a mile.

Screenshots

Screenshot - Pittsburgh Locations page


Screenshot - Washington DC Locations page


Screenshot - Greater Los Angeles Locations page


Engineering notes

• Drupal includes only the location ID. React app connects type to ID.
• Reference: ${facility.attributes.classification} and src/applications/static-pages/facilities/OtherFacilityListWidget.jsx:75

---

Tasks

• [ ] TBD

[mmiddaugh]

May make sense to do along with Update Other nearby locations directions link with sr-only solution #14309

[jilladams]

From refinement: Other Locations on VAMC Systems are manually entered: https://prod.cms.va.gov/node/318/edit

This is an editor management issue, right now.

Noting: Vet Center "Other nearby VA locations" behaves differently. It's build programmatically, and not manually entered.

In the future, when hardening VAMCs, we may want to revisit the logic for how this is handled and make this programmatic as well. For VBA, we also want to make that programmatic.

[jilladams]

Other locations where this applies:

• https://www.va.gov/asheville-health-care/locations/ -- for this item, Asheville reported an issue to helpdesk that can be mitigated by themselves. We need to work with @TroyA6 @stefaniefgray on follow up there. https://dsva.slack.com/archives/C02730UEZPS/p1689017055317939. #14224