==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]