While we're waiting for event logging stuff to be sorted, I'm going to add actual traffic (which uses webrequest data) as a thing.
Fri, Jun 23
Chelsy and I talked about this and seeing as there is a need for faster A/B test report turnaround, she'd like to take lead on this project. Notes from our discussion:
Thu, Jun 22
Will be deploying the homepage with the footer soon (https://gerrit.wikimedia.org/r/#/c/360592/ is ready to be +2'd/merged by Mr. G) but the deployed dashboards have the footers and the repos have the licenses.
I followed @hashar's instructions (I didn't even know about the access GUI!) and everything works perfectly now. Thank you!
Wed, Jun 21
Tue, Jun 20
Aiming to update the index page to be:
Up and announced: https://lists.wikimedia.org/pipermail/wikitech-l/2017-June/088374.html
@Andrew it works now, thank you!
@chelsyx is it OK to also add "This page is available under the Creative Commons Attribution-ShareAlike License." to the footers of the index page & dashboards? We'd also include a link to the index page.
Sat, Jun 17
Fri, Jun 16
Unfortunately the UI code changed in a way to invalidated my event logging patch :( the SERP code will need to be patched to include data that had been removed.
- action = "hover-on" and "hover-off"
- if the user moves mouse from one section to another (e.g. related pages to categories), that's two pairs of on-off hover events
- in case of action == "hover-on", extraParams should have a stringified-JSON object of the following data:
- hoverId: an ID generated randomly & saved upon hovering over a new result, used for pairing with "hover-off" events
- section: "pages"|"categories"|"languages"
- results: ## (0 if no results)
- in case of action == "hover-off", extraParams should have a stringified-JSON object of the following data:
- hoverId: the same ID used from the "hover-on" event, cleared upon hovering off until user hovers over another result
- action = "esclick" for when the user clicks on one of the explore similar links
- extraParams.hoverId = same ID used from "hover-on" event
- extraParams.section = "pages"|"categories"|"languages" (used for consistency checking)
- extraParams.result = # of the clicked result (e.g. 1 for 1st result) if in related pages or categories; name of clicked language otherwise
Thu, Jun 15
I just tried it again and I'm still getting the same error. I also tried it after logging out and logging back in (might as well try that, right?) but also to no success.
BTW, now that T161354 is done, Ops/Puppet has a Shiny Server module: https://github.com/wikimedia/puppet/tree/production/modules/shiny_server
Test instance up and running at https://discovery-dev.wmflabs.org/
Wed, Jun 14
Fixed and deployed to production.
@chelsyx and I are considering the MIT license but we have a question we're going to ask Legal about.
Taking a look...
Thu, Jun 8
Update: apparently the feature will go live on the train next week. Once it's live, I'll check to see if we're collecting the data we expect to be collecting.
Wed, Jun 7
Sys.setenv(HADOOP_CONF_DIR = "") Sys.setenv(HADOOP_HOME = "") Sys.setenv(HADOOP_PREFIX = "") Sys.setenv(YARN_CONF_DIR = "")
I downloaded spark-1.6.3-bin-hadoop2.6 (http://spark.rstudio.com/#installation uses Spark 1.6.2) and put it in my homedir on stat1002 and have the following in my .bashrc:
Tue, Jun 6
Also for future reference: RStudio (the folks behind Shiny) are making a PhantomJS-based thing for automated testing of Shiny applications: https://rstudio.github.io/shinytest/
Thanks for finding the source of the problem, @Gehel!
Top combinations (that had >200 searches on 1 June 2017):
Mon, Jun 5
Sun, Jun 4
Counts of advanced Special:Search searches for each observed combination of namespaces on 1 June 2017. The proportion is how many searches out of total namespace searches within the wiki -- e.g. the 1.6K Category + File searches accounted for 20% of the advanced Special:Search searches.
Fri, Jun 2
New query that actually does the thing desired (keeping previous one just for future reference):
Wed, May 31
Another note for event logging: we may want to include tracking of accept-language, especially for assessing the engagement with similar results from other languages.
@chelsyx: okie dokie, the files have been moved/copied, golden and polloi have been updated, dashboards have been updated/tested/deployed
May 25 2017
Current draft of Hive query for extracting namespace and counting searches:
I'm not a power searcher, so if someone could kindly provide a few (say, 3 or 4) example search queries that illustrate multi-namespace searching, that would be super helpful. (Please and thank you.)
May 21 2017
May 10 2017
@TJones & @Deskana: for this, do you want the overall ZRR from well-behaved searches or broken down in some way? e.g. type (completion suggester vs full-text) or wiki? (In which case it would be added to https://discovery.wmflabs.org/metrics/#langproj_breakdown
May 9 2017
Eventlogging needs to capture:
- if the user hovered over the 'explore similar' link (to open the listings)
- this will also capture if the user clicked on the link
- if the user hovered over the same 'explore similar' link (to close the listings)
- this will also capture if the user clicked on the link
May 8 2017
May 5 2017
I have a ops-puppet repo patch ready to submit once T164603 is done and/or if there's a change-id that I can specify for Depends-On
May 1 2017
Good job, @chelsyx!
Apr 28 2017
Apr 27 2017
Apr 26 2017
Apr 25 2017
Apr 24 2017
Final draft updated on GitHub & uploaded to Commons: https://commons.wikimedia.org/wiki/File:Second_Test_Of_Cross-wiki_Search_-_Helping_More_Users_Discover_Content_On_Wikipedia%E2%80%99s_Sister_Projects.pdf
Apr 21 2017
We're leaving this up on beta for a few more days just in case anyone discovers a major bug. If we don't hear of any problems, we'll deploy it to production at the beginning of next week.
2nd draft up now :) unless anyone objects, I'll upload the PDF to Commons on Monday
Apr 20 2017
I deleted all the counts from 2017-02-18 onward (which is as far back as we would be able to backfill) and our pipeline is currently recounting the requests :) The annotation will be visible in production in the next round of dashboard deployments, but it's on beta now https://discovery-beta.wmflabs.org/wdqs/
Apr 19 2017
Apr 18 2017
Apr 17 2017
I'd also recommend adding a "description" field that each report can have. Our config YAMLs have those (e.g. https://github.com/wikimedia/wikimedia-discovery-golden/blob/master/modules/metrics/external_traffic/config.yaml) and it's super useful for generating https://datasets.wikimedia.org/aggregate-datasets/discovery/README.md: