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

URL Change for: Brunswick VA Clinic - DUBLIN - CLOSURE (Awaiting REDIRECT) #19624

Open
4 of 16 tasks
TroyCMSSupport opened this issue Oct 28, 2024 · 1 comment
Open
4 of 16 tasks
Assignees
Labels
Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Flagged Facilities Facilities with flags requiring follow-up Redirect request sitewide User support Workstream: The customer journey of CMS users, from onboarding to support services, etc.

Comments

@TroyCMSSupport
Copy link

TroyCMSSupport commented Oct 28, 2024

Parent ticket: #19269

Implementation date

When does this request need to be live:
ASAP

Instructions for URL redirect

(Note: This issue will be used from initial request through implementation to ensure all individuals working on this are notified of status updates. Please do not create multiple issues to track different steps.)

  • Notify VA stakeholders as appropriate.
  • Link the related facility closure / rename issue.
  • Create a URL redirect in the vsp-platform-revproxy repo in template-rendering/revproxy-vagov/vars/redirects.yml
  • Add the "Awaiting redirect" flag to the facility node with a revision log message that includes a link to this ticket, preserving the node's current moderation state.
  • Redirects deploy daily except Friday at 10am ET, or by requesting OOB deploy (of the revproxy job to prod) in #vfs-platform-support. After deploy, validate that the URL redirect is deployed. (Note: In the event of a facility closure or a name change, validate that this occurs before making the Lighthouse csv changes.)
  • Update this ticket with a comment that the redirect has been deployed.
  • Remove the "Awaiting redirect" flag on the facility node with a revision log message that includes a link to this ticket, preserving the node's current moderation state.
  • Notify helpdesk via comment on ticket or Slack message in #cms-support that changes are ready for review.

URL Redirect

Current URL Redirect Destination or New URL
https://www.va.gov/dublin-health-care/locations/brunswick-va-clinic https://www.va.gov/charleston-health-care/locations/brunswick-va-clinic

Use one of the following:

1. Canonical URL change

Note: Canonical URL changes do not block the completion of the parent ticket. Once the URL redirect above has been deployed, the value to the Veteran is delivered. This ticket should be kept open until the URL change is verified, except in the case of a removal (as described below).

Instructions for canonical URL change

  • Verify that the new URL for the facility is published and accessible on VA.gov.
  • Contact Lighthouse via Slack at #cms-lighthouse channel that this facility requires a canonical link in the following format (replacing the placeholder data with the actual API Id and VA.gov URL):
    • vha_557GE,https://www.va.gov/charleston-health-care/locations/brunswick-va-clinic/
  • Add the "Awaiting CSV" flag to the facility node with a revision log message that includes a link to this ticket.
  • Let Help desk know this has been done, if not done by Help desk.

Wait (days or weeks, potentially)

  • After the canonical link has been added to the websites.csv and you have confirmation from Lighthouse that the CSV has been deployed, validate that the change has deployed by checking that the Facility Locator has been updated with the new url.
  • Update this ticket with a comment that the CSV change has been deployed.

URL change example (update with actual ID and URL)

Facility API ID Full VA.gov URL
vha_557GE https://www.va.gov/charleston-health-care/locations/brunswick-va-clinic/

2. Canonical URL removal (if removed from VAST)

Instructions for canonical URL removal

  • Try to find the facility via the Facility Locator, using the Facility API ID (e.g. https://va.gov/find-locations/facility/"facility_api_id"). If it is not available, proceed.
  • Contact Lighthouse via Slack at #cms-lighthouse channel that this facility requires a canonical link to be removed in the following format (replacing the placeholder data with the actual API Id and VA.gov URL):
    • vha_557GE,https://www.va.gov/charleston-health-care/locations/brunswick-va-clinic/

Note: there's no check to see if it's not returning anything, as it should already be not showing anything in the Facility Locator.

@TroyCMSSupport TroyCMSSupport added Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Flagged Facilities Facilities with flags requiring follow-up Redirect request sitewide User support Workstream: The customer journey of CMS users, from onboarding to support services, etc. labels Oct 28, 2024
@TroyCMSSupport
Copy link
Author

@omahane @ian-sears --
Should this redirect move forward so that the Dublin / Brunswick site can be archived?
The NEW Brunswick site (under Charleston) is already in place -
Your thoughts? Suggestions?

@TroyCMSSupport TroyCMSSupport changed the title URL Change for: Brunswick VA Clinic - DUBLIN - CLOSURE (Awaiting VAST) URL Change for: Brunswick VA Clinic - DUBLIN - CLOSURE (Awaiting VAST or REDIRECT) Nov 6, 2024
@TroyCMSSupport TroyCMSSupport changed the title URL Change for: Brunswick VA Clinic - DUBLIN - CLOSURE (Awaiting VAST or REDIRECT) URL Change for: Brunswick VA Clinic - DUBLIN - CLOSURE (Awaiting REDIRECT) Nov 13, 2024
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 Facilities Facilities products (VAMC, Vet Center, etc) Flagged Facilities Facilities with flags requiring follow-up Redirect request sitewide User support Workstream: The customer journey of CMS users, from onboarding to support services, etc.
Projects
None yet
Development

No branches or pull requests

3 participants