Redirect Request: Covid volunteer stragglers

[kristinoletmuskat]

POC	Github alias(es)
Product team point(s) of contact:	@stephenBarrs
IA point of contact:	@kristinoletmuskat

Type of request

• 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?

• Yes - Please note: Redirect still needs approval from IA.
  • 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:
• No hard timing requirements, publish when possible.

Redirects

Current URL	Redirect Destination or New URL
https://www.va.gov/coronavirus-research/volunteer/sign-up and ALL CHILD PAGES	https://www.research.va.gov/for_veterans/
https://www.va.gov/coronavirus-research/volunteer/update/ and ALL CHILD PAGES	https://www.research.va.gov/for_veterans/

Note: for the second link listed, the base URL is already redirecting, but this child page is not: https://www.va.gov/coronavirus-research/volunteer/update/update-form?id=123456abcd

Process, Roles and Responsibilities

• Requesting team: Above information is provided
• 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

[kristinoletmuskat]

@FranECross noting for that second link listed that the base URL is already redirecting, but this child page is not: https://www.va.gov/coronavirus-research/volunteer/update/update-form?id=123456abcd

[jilladams]

@kristinoletmuskat question: this Corona virus research app will also need to be deprecated in the code if it's no longer live, right? Is there not a product team dealing with that? (Maybe the folks who asked for this redirect know?)

[kristinoletmuskat]

@jilladams yes! The team is tracking that from this ticket: #83785 (comment)

[jilladams]

@kristinoletmuskat in the spirit of letting product teams handle their own redirects: could they do this one?

[jilladams]

(Forgive if we're not there yet - I forget where we've landed so far in the process of Sitewide not doing all of them.)

[stephenBarrs]

@jilladams yep we will be deprecating the app code when the redirects are in place (and time/priorities permitting)

[kristinoletmuskat]

@jilladams hey! Yes we decided to continue PW doing all of the redirects until we have sufficient guidance for developers on the platform site. So I think y'all will need to do this one!

[FranECross]

@kristinoletmuskat Acknowledged! Ticket is refined, in Ready, and tagged for the sprint starting on 9/18. Thanks for confirming!

[FranECross]

@kristinoletmuskat Just a quick head's-up that this ticket didn't make it into the sprint that started today due to the silent failure work that was prioritized by Chris. We do have it at the top of the Ready column so that if the team is able to pull it in, they will. Thanks! cc @jilladams

[randimays]

Pulling in as stretch for sprint 13.

[randimays]

@kristinoletmuskat We had a ticket a few months ago for coronavirus-research URLs: #84196. If I combine those requirements with the requirements in this ticket, we end up with Table A. Could this be simplified to Table B instead, or do we need specificity?

Table A

Current URL	Redirect destination
https://www.va.gov/coronavirus-research/ (NO child pages)	https://www.research.va.gov/for_veterans/
https://www.va.gov/coronavirus-research/sign-up/ (ALL child pages)	https://www.research.va.gov/for_veterans/
https://www.va.gov/coronavirus-research/volunteer/sign-up/ (ALL child pages)	https://www.research.va.gov/for_veterans/
https://www.va.gov/coronavirus-research/volunteer/update/ (ALL child pages)	https://www.research.va.gov/for_veterans/

Table B

Current URL	Redirect destination
https://www.va.gov/coronavirus-research/ (ALL child pages)	https://www.research.va.gov/for_veterans/

[kristinoletmuskat]

Yes @randimays I think we can go with table B! When the original ticket came in I was confused about what was a child of what, so some of these got missed. Sorry about that and creating extra work for you.

[randimays]

No need for apologies @kristinoletmuskat I'll get it consolidated 👍🏻

[randimays]

@kristinoletmuskat I have verified that https://www.va.gov/coronavirus-research/ and all child pages redirect to https://www.research.va.gov/for_veterans/. Will you please verify on your end and close the ticket if all is good?

[kristinoletmuskat]

verified in prod, closing