####Background:
Investigate how and where to store the association between an edit and a CampaignEvents event in MediaWiki.
When a user indicates that their edit is related to a campaign event, we need to persist this association in a way that allows efficient querying and reporting later.
We want this data to be able to surface contribution data on pages like the Watchlist, RecentChanges, etc in the future too.
####More information on data usage:
**Question: Where do we show the data in the UI, both in the short-term and long-term?**
* Special:EventDetails (Contribution tab - this would be the full breakdown of info)
* Maybe the event page - I can imagine people wanting the impact data being visible on the actual event page rather than only found through EventDetails - would there be a way to transclude that tab in the future? We don't need to have an answer now, but it is something to consider.
* Special:Watchlist - a tag/some way of identifying that the edit is from the event, and ideally it would link to the event page/contributions tab
* Special:RecentChanges - a tag/some way of identifying that the edit is from the event, and ideally it would link to the event page/contributions tab
What kinds of reports will people want in the future related to the data?
####Acceptance Criteria:
* This task is focused on identifying:
- The data structure required (e.g. revision ID and event ID).
- Any relevant constraints or indexing considerations.
- Where to store the data
- Consider what would be the most flexible approach, since we cannot predict everything in advance
- Consider how we can potentially support many different types of edits (such as a moderator backlog drive that has people reverting edits or deleting pages - example, [[ https://en.wikipedia.org/wiki/Wikipedia:New_pages_patrol/Backlog_drives/May_2025 | NPP backlog drives ]])
- Consider how we can surface contribution data on pages like the Watchlist, RecentChanges, etc, so that people can see that an edit is a part of an event
- Consider how we may want to handle reverts
*** We want to display reverted edits rather than having them "disappear" since organizers want to be able to track both legitimate and potentially illegitimate reverts associated with their events so that they can identify gaps in editing knowledge among their participants or potential discrimination/moments to defend edits
* We may need to check in with Editing team