Investigate ways to report out on currently available campaign-events data.
The campaigns engineers are working on priority engineering items and may not be able to begin data instrumentation and pipelining on T320289 in Q3. Nonetheless, the team needs data for base monitoring and reporting.
Note: the solution is unlikely to be an automated solution; it will focus on simplicity.
Schema
REST API documentation
Gerrit JSON file
Extension:CampaignEvents/campaign_events_table (linked in the infobox in Extension:CampaignEvents)
https://www.mediawiki.org/wiki/Extension_default_namespaces
- query campaigns-event data on wikishared
- query the editor_month table
- sync with Lauren/ @cmelo / valerie to discuss contents and potential tooling
- sync with Lauren/Claudio/Valerie to see if solutions suffice for the interim -- demo reporting outputs
- discuss a reporting frequency - monthly
- assess best table to use for gathering global id, global username, and registration information (date, auto created, api created); reference chart created and double checked with MWW
- adapt setup given input
see also T322751
Test Outputs:
Demo Events Roster Sheet
Ambassador View
Campaign People