Add new fields to searchsatisfaction2 schema
Closed, ResolvedPublic
Actions

Description

The user satisfaction backup KPIs would benefit from some extra data in the EventLogging table. Our proposed additions are:

A per-user UUID that persists for longer than the search session - probably 24 hours.
The (unhashed) search query that the user submitted. (Needed just once per SERP.)
The actual ID (not a pseudorandom ID) of the page that was landed on.
Number of results returned to the user. (Needed just once per SERP.)
The rank of the visited page as it was on SERP.
For check-in events: has the user scrolled the page since the last check-in?

Details

Related Gerrit Patches:

mediawiki/extensions/WikimediaEvents : master	Add new fields to TestSearchSatisfaction
mediawiki/extensions/WikimediaEvents : wmf/1.27.0-wmf.2	Add new fields to TestSearchSatisfaction
mediawiki/extensions/WikimediaEvents : wmf/1.27.0-wmf.3	Add new fields to TestSearchSatisfaction
mediawiki/core : master	Include additional analytics in Special:Search

Related Objects
Search...

		Status	Assigned	Task
		Resolved	Ironholds	T113297 Create backend for speedily computing various ad-hoc user satisfaction KPIs
		Resolved	EBernhardson	T113291 Add new fields to searchsatisfaction2 schema

Event Timeline

Ironholds created this task.Sep 21 2015, 9:11 PM

Ironholds raised the priority of this task from to High.

Ironholds updated the task description. (Show Details)

Ironholds added a project: Discovery-Search (Current work).

Ironholds added subscribers: Ironholds, mpopov.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 21 2015, 9:11 PM

mpopov updated the task description. (Show Details)Sep 21 2015, 9:23 PM

mpopov set Security to None.

mpopov updated the task description. (Show Details)Sep 21 2015, 9:26 PM

Best guess on what needs to be done:

A per-user UUID that persists for longer than the search session - probably 24 hours.

This will have to be stored in localStorage (or a cookie. localStorage is easier and doesn't require caching considerations)

The (unhashed) search query that the user submitted. (Needed just once per SERP.)

As long as its just from the SERP this should be relatively easy. We might want to expose the query directly to javascript (rather than trying to suck it out of the correct input box) by using OutputPage:addJsConfigVars(...) in php and mw.config.get(..) on the javascript side.

The actual ID (not a pseudorandom ID) of the page that was landed on.

This is available in javascript as mw.config.get( 'wgArticleID' )

Number of results returned to the user. (Needed just once per SERP.)

Ideally we should add this via addJsConfigVars as well, but it could be counted from the page structure.

The rank of the visited page as it was on SERP.

The only way i can think of tracking this information is injecting the position into the query parameters and picking that up on page load.

For check-in events: has the user scrolled the page since the last check-in?

The most cross-browser compatible way to get this is probably to check $(window).scrollTop() for the current position to compare against the position at the last checkin.

mpopov added a parent task: T113297: Create backend for speedily computing various ad-hoc user satisfaction KPIs.Sep 23 2015, 6:24 PM

• ksmith added a project: WorkType-NewFunctionality.Sep 24 2015, 4:40 PM

EBernhardson claimed this task.Sep 24 2015, 7:12 PM

EBernhardson moved this task from In Progress to not in use - please delete on the Discovery-Search (Current work) board.

Change 240924 had a related patch set uploaded (by EBernhardson):
Add new fields to TestSearchSatisfaction

https://gerrit.wikimedia.org/r/240924

gerritbot added a project: Patch-For-Review.Sep 24 2015, 11:36 PM

Change 240889 had a related patch set uploaded (by EBernhardson):
Include additional analytics in Special:Search

https://gerrit.wikimedia.org/r/240889

Patch above adds all requested fields. It also goes a little bit further than requested: This adds wprov=srpw1_N to all search results, regardless of being included in the test or not. We can query this back out of the page views tables in hive and have an unsampled look
at what search positions (sorry, doesn't track which actual query the page view is related to. Would be nice but the urls would get all nasty. We would need a redirect bouncer like google at that point (which isn't that hard at all!)).

EBernhardson moved this task from not in use - please delete to Needs review on the Discovery-Search (Current work) board.Sep 27 2015, 4:02 AM

Change 240889 merged by jenkins-bot:
Include additional analytics in Special:Search

https://gerrit.wikimedia.org/r/240889

EBernhardson mentioned this in rMW5014a99c0588: Include additional analytics in Special:Search.Sep 28 2015, 10:32 PM

ReleaseTaggerBot added projects: MW-1.27-release (WMF-deploy-2015-10-06_(1.27.0-wmf.2)), MW-1.27-release-notes.Sep 29 2015, 10:13 PM

Jdforrester-WMF edited projects, added MW-1.27-release (WMF-deploy-2015-09-29_(1.27.0-wmf.1)); removed MW-1.27-release (WMF-deploy-2015-10-06_(1.27.0-wmf.2)).Sep 30 2015, 12:48 AM

EBernhardson moved this task from Needs review to Done on the Discovery-Search (Current work) board.Oct 6 2015, 4:33 PM

Change 240924 merged by jenkins-bot:
Add new fields to TestSearchSatisfaction

https://gerrit.wikimedia.org/r/240924

Change 246119 had a related patch set uploaded (by EBernhardson):
Add new fields to TestSearchSatisfaction

https://gerrit.wikimedia.org/r/246119

Change 246120 had a related patch set uploaded (by EBernhardson):
Add new fields to TestSearchSatisfaction