[CAIA Intake] OCTO Health: Deprecate coronavirus research registration tool

[batemapf]

Content, accessibility, information architecture (CAIA) new initiative collaboration request

Use this ticket to request collaboration on a new initiative with the sitewide content, accessibility, and information architecture (CAIA) team.

About your team

• Team name: OCTO Health
• OCTO product owner: Patrick Bateman
• Product name: Coronavirus research registration tool
• Product manager: Patrick Bateman
• Slack channel: https://dsva.slack.com/archives/C02BTDTEPNH (but best is to just DM Patrick)
• Dedicated content writer on your team (if you have one): N/A
• Dedicated a11y specialist on your team (if you have one): N/A

About your initiative

Which of these descriptions best fits the work we’ll partner on?

Select all that apply.

• [ ] Digitizing a new form
• [ ] Creating a new digital tool
• [ ] Updating an existing form or tool
• [ ] Translating a form or tool into Spanish
• [ ] Adding new unauthenticated content to VA.gov
• [ ] Updating existing unauthenticated content on VA.gov
• [ ] Something else: Turning something off :tada:

What's the nature of your initiative and desired outcomes?

Turn off https://www.va.gov/coronavirus-research/.

Collaboration timeframe

Note: We work on nearly every OCTO product and manage all unauthenticated content on VA.gov, so we will need to prioritize intake requests based on overall workload and VA and OCTO priorities.

Is this work tied to a Congressional mandate, change in law or policy, or upcoming event with a specific deadline?

• [ ] Yes
• [x] No
• [ ] I’m not sure

Where are you at in your timeline?

Tell us briefly about what you're working on now (such as initial discovery, wireframing, or usability research planning) and add any known dates for upcoming milestones or deadlines.

Not urgent to get it turned off, but sooner would be better.

Will you release this new product incrementally (for example, release to 25% of users to start)?

• [ ] Yes
• [x] No

Turn it all off at once.

*Note: **If you check yes, we’ll reach out to discuss details about the content in the react widget. We use these widgets to display entry points for new products to a certain percentage of users who visit our static pages. Please refer to this GitHub reference for dynamic content.

• [ ] I acknowledge that if I change the launch to be incremental, or change it from incremental to 100%, I must notify CAIA of this change as there is additional work involved that may impact deadlines.

Collaboration cycle

Which phases of the collaboration cycle have you completed?

Select all that apply.

• [ ] Design intent
• [ ] Midpoint review
• [ ] Staging
• [x] None. This initiative isn’t going through the collaboration cycle.

Collaboration cycle ticket

If you’re going through the collaboration cycle, provide your ticket number and link:

• Ticket Number: xxxxxx

Supporting artifacts

Provide links to any supporting artifacts that can help us better understand your initiative and begin collaboration. Include artifacts like your product outline, user flows, mockups and prototypes, or any draft content.

• Tool in production today

Next steps

• [x] Post a link to this issue in the #sitewide-content-sitewide-content-accessibility-ia slack channel and tag @Terry Nichols, and we’ll then acknowledge receipt. We'll then review the artifacts in more detail and work with you to determine timing for collaboration. Depending on the work, we may schedule a kickoff meeting to better understand how we'll partner together.
• [x] Review the remaining next steps in the VFS team tasks section here.
• [ ] If you also need engineering support from the public websites team, fill out their intake request form as well: Open a public websites intake request
• [ ] If you're requesting a page/URL redirect, a URL change, or a vanity URL, submit an additional request for this work: Open a redirect, URL change, or vanity URL request
• [ ] If you're creating an experimental design, also contact the design system team: Read more about experimental designs
  Suggest an addition or update to the design system team
• [ ] If you're requesting a11y support for usability research, submit a research support request next: Open an a11y research support request
• [ ] If you are requesting content support, please share your content source of truth (preferably as a SharePoint document).

### Tasks
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/85820

[kristinoletmuskat]

Hey hey @batemapf, when we deprecate a page we always put in a redirect so that the old url doesn't 404 (like if a user has it bookmarked). Do you know where it might make the most sense to redirect this one?

[batemapf]

Maybe https://www.va.gov/coronavirus-veteran-frequently-asked-questions/?

[batemapf]

...alternatively https://www.research.va.gov/for_veterans/

[kristinoletmuskat]

Noting that we'll also need to remove entry points to this link (like this one in the screenshot below on https://www.va.gov/health-care/covid-19-vaccine/)

Of the top of my head, I'm thinking redirecting to https://www.research.va.gov/for_veterans/ might make more sense, since someone bookmarking this link I would say would be primarily interested in research opportunities vs covid-related information.

[kristinoletmuskat]

@strelichl I think we can implement the redirect with public websites and then put the actual drupal page deprecation in the content backlog (since the team is super stretched). I can create the redirect ticket tomorrow.

@batemapf I'm assuming your team owns the tool code for https://www.va.gov/coronavirus-research/volunteer/sign-up -- I'm not sure if we do anything to take old code down other than redirecting it? Do you know?

(note for myself) Will also need to redirect the tool url and all child pages: https://www.va.gov/coronavirus-research/volunteer/sign-up

[kristinoletmuskat]

@batemapf do you have approval from stakeholders that would manage these pages? Or anyone we need to notify?

[kristinoletmuskat]

I just submitted the redirect ticket to public websites: https://github.com/department-of-veterans-affairs/va.gov-team/issues/84196

[stephenBarrs]

@kristinoletmuskat the OCTO Health Engineering team (we work with @batemapf) will remove the old code once the redirect is in place.

[strelichl]

Added backlog ticket to deprecate: #85820

[kristinoletmuskat]

Whoops I just closed this! But see we still need to deprecate.