Discussed this with @ifried today including looking at sample data previously gathered by another team (specifically this chart output).

recommendation: use os_family data (not device_family) when event special pages are added to the pageview whitelist.

Met with @ifried today and talked about the data assets. Here's the preliminary list of potential metrics to track moving forward (which we discussed today):

See the related Slack discussion

Context: In the Measurement Plan we discussed collecting site_category as three categories:
If referrer is in news sites: log it as “news-site”
If referrer is in Media sites: log it as “media-site” and log the domain (e.g. "facebook", "tiktok", "youtube")
If the referrer is in neither list: log it as "non-media-news"

@EliasRut The results shown in T364502#9785662 correspond to 31 unique verification requests; two of those 31 requests are for 04/17. Both 04/17 requests show a related ephemeral id.

1. I've updated the datetime handling to UTC only, dropping Z handling and PST conversion:

@EliasRut thank you for looking into 4/28 and 4/17.
I'll update the ticket description with what you've noted about 03/23 and 03/24.
And I'll look at the analysis code again and will post on what I learn here.
I'll also note here when I post updated notebooks to the repo.

Tried again with a list of 319 page ids. First I pulled campaign event page names, then I pulled page ids for those page names.
This confirms zero no_JS edits on those event pages.
With this approach I see 509 edits total.

As far as event counts:

events_query_count_mariadb = '''
    SELECT 
       COUNT(DISTINCT campaign_events.event_id) AS unique_event_count
    FROM campaign_events 
    WHERE 
        campaign_events.event_created_at BETWEEN "20240101000000" and "20240508000000" OR
        campaign_events.event_last_edit BETWEEN "20240101000000" and "20240508000000"
    '''

Questions from Ilana, to contextualize the task:

Superset: Citation Needed Dashboard

FYI: Next (related) task: T364162

Completed. Output data, since launch date, can be found in tabs in these sheets: Citation Needed Metrics

This analysis builds on the work completed in T240697#7127421 which built on the work in T240697#6217971.

For future reference, instead of event.mediawiki_cirrussearch_request for API requests, we should use

event.mediawiki_api_request

FYI, related: T252227

data compilation sheet

Met with Ilana today and Identified/fixed:
Identified the final list of events (12)
Identified which workbooks had different columns than the others (3)
Identified workbooks that needed additional data entry (multiple)
Identified workbooks which had additional extra characters in the username columns (multiple)
Identified workbooks with duplicated names in G username column (1)

Update: The data is stored in a Citation Needed Google drive folder currently accessible by Nat H, Maryana P, Elias, and Irene

Charts that are used on the dashboard:
Daily searches made by Citation Needed API

Met with @ifried today and discussed the calculated rates.
Ilana is interested in the number of people invited from the list and the rate of registration for those people that were on the list AND were invited.

H Match function

Added events from the worksheet Index of Events that used Event Invitations to the data compilation sheet

Interim checkup numbers - compilation sheet - for the campaigns and metrics noted above

About the wprov CTR query:
Related: T342069
Citation Needed wprov conversation reference on Slack

About the Cirrus Search query:
Related: T341743
Plugin DAG
Plugin hql query

FYI: two potentially related tickets: T240697 and T251464 (and also T263505) and T234695#6481955 for readers data

DRAFT Brief

Added this note:
"If you are using this table to calculate editor regional data and would like to read about the nuances in source table calculation methods and approaches, refer to this deep dive on Phabricator: T334363"