Redirect Request: Old Operating Statuses to new ones

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:	@jilladams @Agile6MSkinner
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

On VAMCs, there used to be an old style of page for Operating Statuses. Long ago, a new format of Operating Status page shipped, but for whatever reason the old pages weren't deprecated at that time. We'd like to do that now. Do you prefer we set up redirects for all the old pages? An example:

Old page: https://www.va.gov/greater-los-angeles-health-care/status/ - not in the site sidebar, not top Google result, not in page 1 site search results
Proper, current page: https://www.va.gov/greater-los-angeles-health-care/operating-status/ - reachable from the sidebar, top Google result, on page 1 site search results

Process, Roles and Responsibilities

[x] Requesting team: Above information is provided
[x] Requesting team: All appropriate VA stakeholders are notified as appropriate
[ ] IA: Request is vetted and documented and implementation plan is clear
[ ] IA: Request is assigned to appropriate team for implementation
[ ] Implementation team: Work is complete
[ ] Implementation team: Validated in production
[ ] Requesting team: Validates everything is correct in production and closes ticket

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

Redirect Request: Old Operating Statuses to new ones #97101