Redirect Request: Family member hub phase 2

[kristinoletmuskat]

Status

[2024-07-29] [Fran] Removed Sprint 9 tag based on info from Kristin, but leaving in Next Refinement so that it'll be ready to go when we're given the green light. (from Kristin: This initiative is delayed (we are planning to go into SME review on 8/5, and anticipate that taking 2-3 weeks realistically). We'll update you in this ticket when we have a better sense of timing!) [2024-07-12] [Fran] Moved to Next refinement and tagged with Sprint 9 (07/23 to 08/06).

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 differnt steps.
• It is your responsibility to notify VA stakeholders as appropriate.

POC	Github alias(es)
Content point of contact:	@laurwill
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 need Public Websites to implement this redirect?

• [x] Yes
• [ ] No - Please note: Redirect still needs approval from IA and PW will do PR review

Implementation date

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

• [x] On a specific date, connected to a program or publishing requirement. DATE: aim to publish & merge redirects by EOD Monday 8/5, to deploy 10am Tuesday 8/6 See Kristin's comment

Redirects

Current URL	Redirect to	Status
https://www.va.gov/COMMUNITYCARE/programs/dependents/champva/champva-claim.asp	R+S: File a champva claim (URL TBD)	Waiting for content to finalize H1
https://www.va.gov/COMMUNITYCARE/programs/dependents/spinabifida/spina-claim.asp	R+S: File a spina bifida claim (URL TBD)	Waiting for content to finalize H1
https://www.va.gov/COMMUNITYCARE/programs/dependents/pharmacy/meds-by-mail.asp	R+S: Meds by mail (URL TBD)	Waiting for content to finalize H1
https://www.va.gov/COMMUNITYCARE/programs/dependents/champva/CHAMPVA-faq.asp	R+S: Getting care through champva (URL TBD)	Waiting for content to finalize H1
https://www.va.gov/disability/eligibility/special-claims/birth-defects/	Spina Bifida page (URL TBD)	Waiting for content to finalize H1
https://www.va.gov/COMMUNITYCARE/programs/dependents/CLFMP.asp	Camp Lejeune page (URL TBD)	Waiting for content to finalize H1
https://www.va.gov/COMMUNITYCARE/programs/dependents/cwvv/index.asp	Children of women vietnam veterans page (URL TBD)	Waiting for content to finalize H1
https://www.va.gov/COMMUNITYCARE/programs/dependents/spinabifida/index.asp	Spina Bifida page (URL TBD)	Waiting for content to finalize H1
https://www.va.gov/COMMUNITYCARE/programs/dependents/pharmacy/index.asp	R+S: Meds by mail (URL TBD)	Waiting for content to finalize H1
https://www.va.gov/health-care/family-caregiver-benefits/	https://www.va.gov/family-and-caregiver-benefits/health-and-disability/	Waiting for content to finalize H1

Process, Roles and Responsibilities

• [x] Requesting team: Above information is provided
• [ ] Requesting team: All appropriate VA stakeholders are notified as appropriate
• [x] IA: Request is vetted and documented and implementation plan is clear
• [x] 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

[FranECross]

@kristinoletmuskat Quick question ... is it possible to change the release date from Friday? We typically try not to release anything on Fridays, in case any issues are found after the fact, so that folk aren't called on the weekends to fix, or if they aren't available, so that Veterans don't have a poor experience. cc @jilladams

[kristinoletmuskat]

Yes! @laurwill if we need to move from Friday, based on the SME feedback timing do you think we should aim for earlier than 8/2, or the following week?

[laurwill]

Let's do following week — I doubt they'll be ready sooner. So tentatively aim to publish & merge redirects by EOD Monday 8/5, to deploy 10am Tuesday 8/6?

[kristinoletmuskat]

Just updated the ticket with those dates

[FranECross]

Thank you both!

[kristinoletmuskat]

Hey @FranECross , just noting that this initiative is delayed (we are planning to go into SME review on 8/5, and anticipate that taking 2-3 weeks realistically). We'll update you in this ticket when we have a better sense of timing!