GPL-nnn As a Dev Mgr (Tom W) I would like developers to be able to deprecate events to simplify the process of patching the databases

[TWJW-SANGER]

User story
As a Dev Mgr (Tom W) I would like developers to be able to deprecate events to simplify the process of patching the databases

The original design of the events warehouse assumed that events and their associated data are immutable.
However in practice much of the data in the events or events themselves are triggered by user inputs which are often incorrect. When patching these errors, fixing or recreating the events involved is time consuming.
By building in the ability to mark events as deprecated we will hopefully make this easier or even eventually automatic.

Who are the primary contacts for this story
Rich L
Tom W
James G

Acceptance criteria
To be considered successful the solution must allow:

• Developers must be able to mark N events as deprecated (ideally this through the API to allow automation)
• Documentation provided on how to use the deprecation feature
• Published queries on Confluence, particularly Heron reporting and MLWH example queries, that involve events need to be updated
• The feature should be announced on the MLWH user group email
• Heron and UKB WIP reporting may need user stories created to update their functionality

Dependencies

Additional context