Update data QA on 2023-03-15, see QA notebook for details.

In T312624#8681550, @Aklapper wrote:

@mpopov: Meh, bugs... Drag and drop to Blocked solved it

Added charts for total number of images added and the number of users reached through image suggestion notifications.

Dashboard in Superset: Image Suggestion Notification Dashboard

Charts in Superset to monitor changes in virtual pageviews on Special:Search page.

Please find the stats for the search preview on desktop in January below. The data is from 01/05/2023 across three Wikipedia: Indonesian, Portuguese, and Russian.

Here are some stats for links per article.

• The count includes Wikipedia and Wikidata.
• I didn't see any links to Wikispecies in wikidata_entity table even though the article has Wikispecies link to it.
• Most of the articles have 2 links to other projects. And the max number of links per article is 7.

@Sneha yes, I sent the data over Slack yesterday.

Thank you @Etonkovidova, I update the QA in production here T324707#8576312

The data QA of the instrumentation in production done on 2023-01-31. See QA notebook for details.

@SWakiyama Sure, I will update the descriptions.

@matthiasmullie i confirm the description works, and update the instrumentation document

1. Yes, when clicking on the same result, we are expecting "close-searchpreview" events.

@Etonkovidova thanks for checking! I will update the QA ticket T324707

@matthiasmullie I am not sure who is the right person to merge these.

According to the measurement spec, we should include track both clicks on QuickView and clicks to objects that don’t have QuickView, and split between these clicks.

In T321070#8329887, @matthiasmullie wrote:

@cchen Do we also want to capture when users click on the placeholder (while the image is still being transferred)? I suspect not?

In T321080#8329849, @matthiasmullie wrote:

@cchen I assume we also want this 'quickview-close' event to be captured when a user leaves the page (while quickview was still open)?

Yes!

@matthiasmullie i confirm we can cross-referencing with SearchSatisfaction to get this data.

In T307572#8291127, @SimoneThisDot wrote:

@cchen Please find below our initial findings/assumptions and questions that we have regarding the proposed instrumentation document.

Schema
it appears as if we’d only need 1 schema, with all this data; I think we should be able to track all of this data for all these events, and it should provide everything analytics needs in order to answer the questions listed:

1. action name (open-quickview|close-quickview|click-image|click-section|click-article-section|click-interwiki-commons|click-interwiki-links)
2. timestamp (will come back to this)
3. wiki id (mw.config.get( 'wgDBname' ))
4. platform (will come back to this)
5. bot (will come back to this)
6. anon (mw.user.isAnon())
7. session id (will come back to this)
8. result position (not yet available, but we could expose the position via wgSpecialSearchTextMatches; will come back to this)

Assumptions - Our understanding of the requested data

1. Number of quickviews open: total number of events with action = ‘open-quickview’
2. Number of search sessions using quickviews: total of events with action = ‘open-quickview’ with unique session id
3. Number of clicks on images in quickview: total of events with action = ‘click-image’
4. …same for snippers, sections, article sections, interwiki-commons & interwiki links…
5. Click through position of quickviews: I’m not yet sure what exactly “click through” means, but available actions + result position ought to suffice
6. Quickview open timestamp; Quickview close timestamp & dwell time - available via action=open-quickview|close-quickview + timestamp

A first pass on the analysis of image suggestion notifications can be found in this Jupyter notebook. The data is from 07/20/2022 - 08/31/2022.

In T307572#8280645, @CBogen wrote:

In T307572#8280503, @cchen wrote:

In T307572#8269070, @matthiasmullie wrote:

Is there anything new that we'll need to instrument? If so, any guidance would be appreciated - what kind of data would need capturing?

Yes, here's a list of metrics and events we want to track https://docs.google.com/spreadsheets/d/1drMnPt8mJa8rQRNCCpgkOo_0eQmdDlHDQnLIbjg8syU/edit#gid=0

@cchen should I move this to our code review column for SD engineers to review? Are we now in the step "Engineers review the event list and comment on whether we’re already tracking with existing instruments and if new instrumentation is required. New tickets created for any new instrumentation needed" listed in the description of this ticket?

In T307572#8269070, @matthiasmullie wrote:

Is there anything new that we'll need to instrument? If so, any guidance would be appreciated - what kind of data would need capturing?

Updated dashboard with all projects, added project and project family filter.

Added weekly click through rate of Sister project widgets on Special:Search in this dashboard: https://superset.wikimedia.org/superset/dashboard/391/?native_filters=%28%29

Here's the link to the new media search dashboard: https://superset.wikimedia.org/superset/dashboard/382/?native_filters=%28%29

In T312063#8123770, @CBogen wrote:

@cchen what's the difference between this new dashboard and https://superset.wikimedia.org/superset/dashboard/236/, aside from adding a project column so it's not just Commons Wiki?

Close this ticket due to Superset timeout issue.
Create a media search dashboard instead T312063

The stats on bluelink edits for ruwiki, ptwiki and idwiki are below. I'm happy to discuss those and add more information.