Redirect Request: Modernized VBA Regional offices as of 9.5.2024

[mmiddaugh]

Instructions

• Requests must be submitted AT LEAST 2 weeks in advance. Some requests take a significant amount of time and coordination to implement, so start the process as soon as you know you will need one.
• 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.
• It is your responsibility to notify VA stakeholders as appropriate.

POC	Github alias(es)
Product team point(s) of contact:	@Agile6MSkinner @jilladams
Content point of contact:	CAIA will enter
IA point of contact:	@kristinoletmuskat

Type of request

• [x] We are retiring or taking down a page and need to redirect the URL (complete redirect section)
• [ ] We are changing the URL of an existing page (complete redirect section)
• [ ] We need a custom vanity URL (complete vanity URL section)
• [ ] We are removing a temporary redirect (add relevant background and link to original redirect request)

Do you have a product technical team able to implement this redirect?

• [x] Yes - Please note: Redirect still needs approval from IA.
  • [x] Please verify your team has reviewed Redirect governance and Redirect technical implementation information
• [ ] No - CAIA will need to make Public Websites aware of the ticket.

Implementation date

When does this request need to be live? NOTE: Redirects in vsp-platform-revproxy auto-deploy M-Th. Friday launches should be avoided. Choose one:

• [ ] On a specific date, connected to a program or publishing requirement. DATE:
• [ ] Any day prior to a deadline/latest possible date. DEADLINE:
• [ ] Any day after an earliest possible date. EARLIEST DATE:
• [ ] During a specific date range: EARLIEST DATE TO LATEST DATE:
• [x] No hard timing requirements, publish when possible.

Redirects

Current URL	Redirect Destination or New URL
https://www.benefits.va.gov/anchorage/	https://www.va.gov/anchorage-va-regional-benefit-office-at-colonel-mary-louise-rasmuson-campus-of-the-alaska-va-healthcare-system/
https://www.benefits.va.gov/ROANCHORAGE/	https://www.va.gov/anchorage-va-regional-benefit-office-at-colonel-mary-louise-rasmuson-campus-of-the-alaska-va-healthcare-system/
https://www.benefits.va.gov/honolulu/	https://www.va.gov/honolulu-va-regional-benefit-office-at-spark-m-matsunaga-department-of-veterans-affairs-medical-center/
https://www.benefits.va.gov/ROHONOLULU/	https://www.va.gov/honolulu-va-regional-benefit-office-at-spark-m-matsunaga-department-of-veterans-affairs-medical-center/
https://www.benefits.va.gov/huntington/	https://www.va.gov/huntington-va-regional-benefit-office
https://www.benefits.va.gov/ROHUNTINGTON/	https://www.va.gov/huntington-va-regional-benefit-office
https://www.benefits.va.gov/losangeles/	https://www.va.gov/los-angeles-va-regional-benefit-office
https://www.benefits.va.gov/ROLOSANGELES/	https://www.va.gov/los-angeles-va-regional-benefit-office
https://www.benefits.va.gov/oakland/	https://www.va.gov/oakland-va-regional-benefit-office
https://www.benefits.va.gov/ROOAKLAND/	https://www.va.gov/oakland-va-regional-benefit-office

And all child pages, and variants of capitalization, e.g.

• www.benefits.va.gov/ROHONOLULU*
• www.benefits.va.gov/honolulu/*
• www.benefits.va.gov/Honolulu/* Use catchAll for all

These are page level redirects for a Teamsite using the injected header -- it can be done within proxy rewrite as a client-side redirect

Process, Roles and Responsibilities

• [x] Requesting team: Above information is provided
• [x] IA: Request is assigned to appropriate team for implementation
• [ ] Requesting team: All appropriate VA stakeholders are notified as appropriate
• [x] Kristin: review the original URLs in the redirect request and do discovery on child pages, casing issues, and potential alternate versions.
• [x] Kristin: report findings in the redirect ticket + tag Michael Skinner
• [x] Michelle and Michael: determine how to handle each case and provide direction back in the ticket, tag Kristin
• [x] Kristin: update the redirect ticket to reflect additional requirements for the redirect (child pages, casing, additional pages, etc) and assign to PW for implementation
• [ ] Implementation team: Work is complete
• [ ] Implementation team: Validated in production
• [ ] Requesting team: Validates everything is correct in production and closes ticket

[mmiddaugh]

Note: a few others are pending so I'm marking this draft. Will add any others which are published this week and remove the Draft note in the title when ready

[jilladams]

Updated ticket body to add the RO versions as explicit separate URLs that need redirects, bc I don't think one rule in the redirects file will be able to handle both versions / easy to miss when engineers are scanning through.

@kristinoletmuskat @strelichl ready for your review.

[jilladams]

(Rolling the content audit for these into #19073 )

[kristinoletmuskat]

Hey @Agile6MSkinner and @mmiddaugh, I checked the casing for these and we just have the 2 variations -- /city/ and /ROCITY/, which are included in the above directions. So I think @jilladams we're good to go.

[Agile6MSkinner]

I created an epic to add VBA redirect requests and added this ticket to it

[jilladams]

Note: once these are all verified, there are 2 Drupal content edits that also need to be made for https://github.com/department-of-veterans-affairs/va.gov-cms/issues/19073. I'll get to those by end of sprint.

[jilladams]

Verified that these redirects are working correctly in prod. I spot checked child pages as well. Closing.