Page MenuHomePhabricator

investigate: Interim campaign-events reporting options
Closed, ResolvedPublic

Description

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

Event Timeline

Iflorez triaged this task as Medium priority.
Iflorez moved this task from Next 2 weeks to Doing on the Product-Analytics (Kanban) board.
Iflorez updated the task description. (Show Details)
Iflorez updated the task description. (Show Details)
  1. Last meeting: I met with Claudio/Lauren/Valerie in the first week of February and discussed outputting three sheets of raw data on events/editors/organizers that are cumulatively updated each month using Jupyter Notebooks on the Statboxes that read out to excel sheets using Gspread + summary sheets on events/editors/organizers (+ regional breakouts thereof if time).
  1. Base sheets update: Using gspread will be complicated due to security concerns. Further, there are details to work out on how to handle participant and organizer sheets. Instead of three roster style sheets of data, to simplify the process and get base reporting started, I've focused on outputting a single roster style sheet on events each month which lists the previous months created events and active events: Demo Events Roster Sheet I welcome feedback on this sheet. What is missing? What is confusing? What needs to be broken out? What shall we remove? How can columns G-K be most helpful, if at all?
  1. Summary sheets: Summary data remains useful and we'll need to define further which framing would be most helpful:
    • Events (previous month's roll up):
      • Number of events: open/active, closed, creations, number of participants, number of organizers, number of new organizers/participants, etc.
    • Participants Roll-up: tenure, project families edited in, # of wikis edited previously, edit bucket
      • by event? by event-participation count? (tenure for those that have participated in 1 event, 5 events, 10 events, 10+ events), etc., by organizer?
    • Organizers:
      • TBD
  1. New campaign event editors: A next step on reporting is calculating the number of new editors for each campaign. T329382 is a dependency on that step

Notes from meeting with @Sadads on Feb 7th (notes):
Events View:
Events (active, not created...provides scope and shows impact; redundancy over months doesn’t negatively impact)
Participants #, Participants New #, Organizer#

Also, It may be interesting to signal when x events were active in previous months.

FYI: Related Slack thread with Georges Fodouop (Feb 5) and (Feb 17)

completed:

  • check to see if Ambassador view (link, country, organizer name) is helpful to output monthly
  • calculate event_roll_up
    1. of active events (with # of participants and new P.) -- events where event_start_utc is in current month (and not deleted_at)
    2. of event registers (with # of participants and new P.)-- events where event_created_at is in current month (and not test events)
    3. of event registers that are test events
    4. of event deletes -- deleted_at

Thank you @JStephenson and @Sadads for your feedback.

We're moving forward with the reporting as shown in the Ambassador View...and including the chat cleaned up field that appears in the Demo Events Roster Sheet...and the roll ups that appear in T334635 (unique events/organizers/participants on the tool and pageviews on tool events)