Evaluate ECA framework for other use cases

[mmiddaugh]

Description

We're excited about the possibility of applying the new ECA framework to other use cases. We need to understand the types of scenarios which are reasonable for this framework and the associated general level of effort so that we can prioritize accordingly.

Scenarios for evaluation

• Moderation state as a trigger for a notification

  • example: when an editor saves content as "in review", a supervisor/approver is automatically notified by email
    • assume the recipient exists at a different level than the editor (not identical sections)
  • example: editor or supervisor/approver is notified when content has been stagnant (no moderation state change for x period)

• Outdated content iteration

  • example: VHA editors are reminded to update/review and validate certain content (such as a mental health number) with different cadence from other outdated content notifications

• Automating processes

  • flagged facility processes
    • example: new facility can be published once editor does x - when x is complete, node is auto published
  • forms processes
  • when new form seen following migration, CAIA is notified
  • content meeting certain criteria (i.e., time since creation) is auto archived
  • content is auto-archived or replaced on defined date/time
  • example: Vet Centers have spotlights they use to promote outreach activities. If the date of the event has passed, the spotlight could be auto-archived or automatically replaced by evergreen content which is not time sensitive

• User management

  • example: generate list of editors who have not accessed Drupal in x period of time and email it to leadership (or remove access)
  • example: editor who has completed training is automatically assigned role/permission

• Content delay notifications

  • example: when content build is delayed by x period of time, post Drupal banner
    • when delayed by y period, send an email to notify editors

• Publication of KB article or release notes node triggers notification on dashboard (or email to specific editor type)

CMS considerations

CMS team needs to learn ECA and will be involved in applying it to future use cases. If we can loop CMS engineers (Jake Bapple, primarily) in on discussions / usage / use cases, that is a desired outcome.

Acceptance criteria

• [ ] For each use case, indicate whether the framework is
  • [ ] possible
  • [ ] a rough estimate of time/difficulty
  • [ ] factors or dependencies which should be considered
• [ ] cc Jake Bapple when you post findings

[mmiddaugh]

@EWashb for awareness

[FranECross]

@dsasser @jv-agile6 This seems like it would be a big enough effort to have this be a spike, or a research ticket that would be pointed and placed in a sprint, instead outside it. Do you concur? Thanks in advance!

[FranECross]

Who is supervisor/approver for a particular node, and other questions that Daniel will enter into the ticket.

[davidmpickett]

@dsasser I'm not sure how far you've gotten on this given the priority of Banners. This is something I am interested/willing to help with

[dsasser]

@davidmpickett just seeing this but I'll be done by COB today, sorry I would have been happy to have you involved earlier. If you want to take a second look I'm sure there are things I incorrectly interpreted from the given scenarios, and having you look at it would help me feel better about the accuracy.