Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CONSIDER] Temporary location override #17144

Open
mmiddaugh opened this issue Feb 5, 2024 · 1 comment
Open

[CONSIDER] Temporary location override #17144

mmiddaugh opened this issue Feb 5, 2024 · 1 comment
Labels
Drupal engineering CMS team practice area Needs refining Issue status VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team Vet Center CMS managed product owned by Facilities team

Comments

@mmiddaugh
Copy link
Contributor

Description

VAST allows a facility to be temporarily deactivated (i.e. renovation) but doesn't provide an easy way to redirect Veterans to a new location where services will be offered in the meanwhile. This is relevant to VAMCs and Vet Centers as Drupal relies on this

Most recent example: Boston Vet Center is undergoing a remodel and services will be split between virtual and in-person services at a different government building which is in a different part of town, with significantly different parking/setting and strict security processes at the entrance. The editor can adjust the "Prepare for your visit" area and the operating status but those still exist in conflict with the displayed address. This conflict is most concerning in the Facility Locator search results.

Problem to solve

How might we accommodate a temporary location on the Vet Center webpage and in Facility Locator search results? What risks need to be mitigated?

@mmiddaugh mmiddaugh added Drupal engineering CMS team practice area Needs refining Issue status VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team Vet Center CMS managed product owned by Facilities team labels Feb 5, 2024
@swirtSJW
Copy link
Contributor

swirtSJW commented Feb 5, 2024

There are largely two issues here:
Drupal: An admin can edit address and contact info of a facility. The CMS sourced pages would reflect this change. That data would persist until something in the Facility API data for that row changed. So there is a risk that a change to hours, or phone number in VAST would cause the address and phone to revert to its original location.
Facility Locator FE: This would need a hard coded override. Once the possibility of an override exists, it would be a low effort to update or add to that override.

FacilityOverrides = [
   'vha_123' => [
       'address_line_1' = '22 Liberty Lane',
       'address_line_2` = 'Suite 5C',
       'city' = 'Rochester',
       'state' = 'NY',
       'phone' = '555-444-1234',
    ],
   'vc_789' => [
       'address_line_1' = '1401 N Potomac Dr',
       'address_line_2` = 'Suite 2',
       'city' = 'Yonder',
       'state' = 'TN',
       'phone' = '777-666-7890',
    ]
]

This would allow for Facility locator and CMS to be brought in sync with the temporary location.

Risk in both cases is that an editor would have to let us know when the address changes back to normal. If we miss that, incorrect data would be served to veterans indefinitely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Drupal engineering CMS team practice area Needs refining Issue status VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team Vet Center CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

2 participants