Hey all, This is the Discovery weekly update for the week of 2017-07-17 _including_ updates from the week of 2017-07-10 because I'm a dummy and forgot to send the update email last week! Feedback and questions are welcome. ==Highlights== * Quarterly Review check-in's were presented this week (links forthcoming). ==Discussions== * Had a good conversation on how we want to do an upcoming A/B test to have search results interleaved [0] * Also had a really interesting conversation on how we should move forward with metrics and KPIs for the Search Platform and Discovery. === Search === * After extensive help and feedback from the Japanese Wikipedia community, we decided ''not'' to deploy the new Japanese language analyzer. [1] * After testing and analysis, we are ''not'' going to deploy the Vietnamese language analyzer [2] * Did some quick analysis of the RelForge impact of initial learning-to-rank model [3] * Completed a high level task of organizing necessary adjustments to the ElasticsSearch learning-to-rank plugin [4] * Updated the Wikidata code to take advantage of nested fields noop script [5] * Analyzing the new Kuromoji Japanese language analyzer is done, just waiting to merge the updated configuration [6] * A/B test for the new search results Explore Similar feature continues after fixing a minor bug [7] [8] * Fixed a mapping bug when using text for 'did you mean' suggestions [9] * Updated the 'cirrussearch-explore-similar-languages-none' message to be more meaningful (will be deployed the week of July 25, 2017) [10] === Analysis === * To track sister project search feature, the Search Metrics dashboard now shows traffic to various Wikimedia projects from Wikipedia search results pages [11] [12] * We found what lowered full-text search PaulScores – it was a change of event logging sampling rates (decreasing enwiki and increasing all other wikis). [13] [14] * Investigated the seemingly odd statistic of mobile web having the highest usage of the sister project snippets in the search results page; conclusion: nothing to worry about, everything is being logged correctly. [15] === Portal === * The Wikipedia portal stats and translations were updated on July 18, 2017 [16] [17] === Maps === * A usage policy was recently changed for the relief data layer that we use in maps to now require an API key; a key was procured and Max S helped us get it into production. This only effected maps on Wikivoyage. [18] [0] https://phabricator.wikimedia.org/T150032 [1] https://phabricator.wikimedia.org/T166731 [2] https://phabricator.wikimedia.org/T170423 [3] https://phabricator.wikimedia.org/T169103 [4] https://phabricator.wikimedia.org/T162062 [5] https://phabricator.wikimedia.org/T166589 [6] https://phabricator.wikimedia.org/T166731#3439190 [7] https://phabricator.wikimedia.org/T149809 [8] https://gerrit.wikimedia.org/r/364834 [9] https://phabricator.wikimedia.org/T155489 [10] https://phabricator.wikimedia.org/T169302 [11] https://discovery.wmflabs.org/metrics/ [12] https://discovery.wmflabs.org/metrics/#sister_search_traffic [13] https://discovery.wmflabs.org/metrics/#paulscore_approx [14] https://phabricator.wikimedia.org/T168466 [15] https://phabricator.wikimedia.org/T170183 [16] https://phabricator.wikimedia.org/T128546 [17] https://phabricator.wikimedia.org/T142582 [18] https://phabricator.wikimedia.org/T170976 --- The archive of all past updates can be found on MediaWiki.org: https://www.mediawiki.org/wiki/Discovery/Status_updates Interested in getting involved? See tasks marked as "Easy" or "Volunteer needed" in Phabricator. [1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R [2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R Yours, Chris Koerner Community Liaison Wikimedia Foundation