Vet Center notifications

[xiongjaneg]

Description

• The goal of VA Directive 6102 is to present information and services to Veterans, caregivers and their families in a consistent and accessible way. To achieve this goal, the directive provides policies and standards that must be followed by all websites within the VA ecosystem.
• CMS has implemented CMS notifications to help editors comply with VA Directive 6102 via reminders to review and update content based on a new "Outdated content" view.
• Currently notifications are being sent to VAMC editors.
• We need to implement notifications to Vet Center editors. This roll-out is intended to begin on October 1, following a return of office hours, and communication to editors by RCS.
• This will be the first time that CMS has a product team implement notifications - some knowledge transfer may be necessary.

Background

• Notifications use flags as triggers
• The Outdated content report is based on the last touched by an editor date, using one year as the definition for "outdated"
• Editors receive an email which links to the outdated content report and the Outdated content audit report KB article
• Product documentation is available in the platform repo: CMS Notifications for VA Directive 6102
• Notification product outline
• Figma design for email
• Directive 6102 KB article
• CMS Notification Triggers and Candidates for Additional Notifications #10139 Triggers for CMS notifications

Screenshots of outdated report

Private Zenhub Image

Private Zenhub Image

Vet Center specifics

Vet Center notifications will follow the VAMC implementation with a few modifications, including

• Vet Center notifications will leverage Vet Center specific email language and KB article (draft in progress)
• Vet Center notifications will have a different cadence than VAMC notifications (twice monthly, beginning in October)

Problems to solve

Spotlights are an important content type for Vet Center editors to review because they are frequently used to advertise events and can become outdated quickly.

• They are not a content type which is specifically surfaced on the outdated content audit report.
• How might we support Vet Center editors in reviewing spotlight content more often?

Tasks

• Finalize language in email (drafted and waiting for approval by Vet Centers)
• Finalize language in KB article (including getting Vet Center content out of existing article, Vet Center article is drafted)

CMS initially framed out the following issues, which are attached to their epic #10477

• Manual queue of Vet Center editor notifications email Manual queue of Vet Center editor notifications email #13045
• Add Vet Centers editor emails to existing tasks.yml Add Vet Centers editor emails to existing tasks.yml #13044

[xiongjaneg]

spotlights, in particular, are used for events and get outdated fast

[xiongjaneg]

Spotlights get outdated fast because they're used for events, how can we monitor these easilty? (unlike content types, which we can view)

[xiongjaneg]

potentially two links in the same email or separate emails with each, may be consistent with national's desire for biweekly notifications:

• report on what's outdated
• section view that's filtered for Facilities

[xiongjaneg]

Oct. 1 is a Sunday. And Facilities Team members have adjacent company offsite responsibilities.

[mmiddaugh]

Updates based on my most recent conversation with RCS - fyi @xiongjaneg

• monthly notification timing
• email will point to KB article rather than to the outdated tool, because of the definition of "outdated" and the ability to identify featured content/spotlight content separately.

[xiongjaneg]

moved future iteration ideas to #16593 and closing completed work