Wikimedia Technology/Annual Plans/FY2019/TEC8: Search Platform/Goals

=Program Goals and Status for FY18/19=

TEC8: Search Platform
 * Goal Owner: Nuria Ruiz
 * Program Goals for FY18/19: Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to discover and search for content.
 * Annual Plan: TEC8: Search Platform
 * Primary Goal is Knowledge as a Service: Evolve our systems and structures
 * Tech Goal: Supporting our Community of contributors



 = Q1 Goals =

Outcome 1 / Output 1
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Incorporate Natural Language Processing (NLP) in the machine learning analysis pipeline for search

Dependency: Will need some short-term consulting help during implementation

Goal(s)

 * Select 1 or 2 NLP applications and prototype the features

Status
July 2018

August 21, 2018
 * Contract contents written up and will start recruiting soon.

September 20, 2018
 * this work continues but the prototype won't be completed in this quarter.

Outcome 1 / Output 2
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Evaluation of image features for search ranking

Goal(s)
Investigate and evaluate image level features for image search ranking (ie. Image quality score in ML indexing) (Stretch goal)

Status
July 2018

August 21, 2018
 * We're using an older test that Miriam Redi created, and meetings / questions and answers are ongoing

September 25, 2018

Outcome 1 / Output 3
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Better understanding of the effectiveness of our improvements to search and the performance of our tooling on the back end

Dependency: Analytics (Audiences)

Goal(s)
Revise search metrics and dashboard

Status
July 2018

August 21, 2018
 * We'll be reaching out to the Research team for assistance and bring them together with our help from Audiences for this goal.

September 20, 2018
 * This is currently ❌ as the Research team is a bit busy with other priorities.

September 25, 2018
 * Analytics is working on the dashboard and documentation of search metrics

Outcome 1 / Output 4
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Improved support for multiple languages by researching and deploying new language analyzers where feasible on individual language wikis.

Goal(s)
Morphological library investigations and implementations (specific languages TBD)

Status
July 2018

August 21, 2018
 * Esperanto plugin is, Malay is ✅, both will need to be deployed into production with other small language bugs in the next couple of weeks.

September 25, 2018
 * ✅ : Esperanto is ✅ and has been deployed and re-indexed. Korean is still.

Outcome 1 / Output 5
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Specific media search filters for Wikidata/Wikibase and the relationships to the topics they represent will be better supported using structured data and other techniques.

Dependency: WMDE

Goal(s)

 * Lexeme search implementation: complete search implementation for all modes for Lemmas and Forms ✅
 * Investigate applying machine-learning enabled ranking to Wikidata searches, start collecting click data for Wikidata completion searches and start developing machine-learning models for Wikidata search relevancy.

Status
July 2018

August 21, 2018
 * Lexeme search work is on-going, but running into a few small issues with the queries and how results are presented and how we want to do this in the future. Also working on extracting cirrus stuff out of Wikibase and getting the Lexemes into the Wikidata query service.

September 11, 2018
 * Lexeme search work is ✅; the models are still but most likely will be part of next quarter's work.

Outcome 2 / Output 1
Technical debt addressed and required maintenance completed for Search Platform components
 * Elasticsearch upgrades and server replacements

Dependency: SRE

Goal(s)

 * Continue to prepare for a major upgrade to Elasticsearch 6
 * Replace Elasticsearch servers which are at the end of their lease ((stalled))
 * Migrate Elasticsearch servers to RAID 0 ✅

Status
July 2018

August 21, 2018
 * Gehel has re-striped everything and migrated the Elasticsearch servers to Stretch. Lease expires on the servers next month; will also be working on migrating other (maps) servers to Stretch.

September 20, 2018
 * prep work is still ongoing, but the data center switch is taking some time away from this work. The actual full upgrade will be part of Q2's work and will require a few weeks of stress testing of the upgrade; also working on the full migration sequence path/documentation/shard checks.

September 25, 2018
 * There is still prep work to be done in Q2 for the ES6 upgrade, will not get to the actual upgrade until Q3, but currently working with local ES6 instances as prep work is being done. Progress on replacement Elasticsearch server procurement is stalled on the quotes and will be done in Q2.

Outcome 2 / Output 2
Technical debt addressed and required maintenance completed for Search Platform components
 * Higher capacity for WDQS to improve its ability to power features on-wiki for readers and the growing set of features for supporting structured data

Dependencies: SRE, WMDE

Goal(s)

 * Add storage to WDQS servers ✅
 * Enable Kafka event consumption
 * Separate the Wikidata Elasticsearch implementation into a separate extension ❌
 * Investigate Blazegraph support options and alternatives (Stretch goal)

Status
July 2018
 * Waiting on discs to arrive.

August 21, 2018
 * Most of the discs have now arrived, need to take the servers offline and re-image them next as growing the cluster is difficult.

September 20, 2018
 * Kafka event consumption is continuing, but separating the Wikidata implementation into a different extension work will be moved to Q2 for completion.

 =Q2 Goals =

Outcome 1 / Output 1
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Incorporate Natural Language Processing (NLP) in the machine learning analysis pipeline for search

Dependency: Will need some short-term consulting help during implementation

Goal(s)

 * Find and hire a contractor to help with NLP work
 * Begin working on one internal NLP project (wrong keyboard detection, starting with Russian/English) (T138958)

Status
October 29, 2018
 * as interviews are on-going, we'll probably start the work in early Q3. Work is now ongoing with wrong keyboard detection.

November 29, 2018
 * Wrong keyboard work is and NLP contractor work will still happen in Q3.

December 13, 2018
 * Contractor has been identified and the contract is starting to be worked on, considering this to be ✅.

Outcome 1 / Output 2
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Better understanding of the effectiveness of our improvements to search and the performance of our tooling on the backend

Goal(s)

 * Improve autocomplete of Wikidata items
 * Expand our machine learning to Wikidata and Commons (autocompletes for relevance, considering multilingual)
 * Prototype a feature that is based on collected data
 * Continued work from Q1 with the collection of click logs for the autocomplete feature

Status
October 29, 2018
 * This is actively being worked on and is fully.

November 29, 2018
 * This is actively being worked on and is fully.

December 13, 2018
 * Trey has this but will probably flow into early Q3 with the NLP contractor.

Outcome 1 / Output 3
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Improved support for multiple languages by researching and deploying new language analyzers where feasible on individual language wikis.

Goal(s)

 * Finish up the Korean morphological library analysis and deploy into production (carry-over work from Q1)
 * This work is dependent on the upgrade to ElasticSearch 6 finishing
 * General language support (i.e, misc language-specific bugs)

Status
October 29, 2018
 * The Korean goal is now ✅ but won't be updated until the ElasticSearch 6.

Outcome 1 / Output 4
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Specific media search filters for Wikidata/Wikibase and the relationships to the topics they represent will be better supported using structured data and other techniques.

Dependency: WMDE

Goal(s)

 * [figuring out what SDC wants]
 * Search for licenses in Commons

Status
October 29, 2018
 * ❌ We are waiting on a few things yet from the SDoC program - hard specs on what is expected from the Search Platform to develop features based off of presentations.

November 29, 2018
 * ❌ We are waiting on a few things yet from the SDoC program - hard specs on what is expected from the Search Platform to develop features based off of presentations.

December 13, 2018
 * This goal is still ❌ as we await further instructions from SDoC program.

Outcome 2 / Output 1
Technical debt addressed and required maintenance completed for Search Platform components
 * Elasticsearch upgrades and server replacements

Dependency: SRE, WMDE

Goal(s)

 * Split the search clusters to increase stability
 * Continue replacing ElasticSearch servers (end of life maintenance) ✅
 * Separate the Wikidata ElasticSearch implementation into a separate extension
 * Migrate ElasticSearch cluster restart scripts as cookbooks using Spicerack
 * Stretch goal: Start working on the CloudElastic replicas (and perform a proof of concept with a few select wikis)

Status
October 29, 2018
 * Quotes from vendors were much higher than expected, Gehel, Erik, and SRE are going over requests and refining configurations to get more within our budget.

November 29, 2018
 * This is still — purchases for the new servers had been made and servers are getting delivered / installed.

December 13, 2018
 * Splitting the search clusters has been ✅ and testing is still (should be done in the next week); replacing the older servers can be considered ✅; separating the Wikidata ES implementation is ✅ but the new extension is still  and will be completed in Q3. Migrating the ES cluster to Spicerack is still  and will need testing.
 * The stretch goal has been pushed to Q3.

Outcome 2 / Output 2
Technical debt addressed and required maintenance completed for Search Platform components
 * Higher capacity for WDQS to improve its ability to power features on-wiki for readers and the growing set of features for supporting structured data

Dependencies: SRE, WMDE

Goal(s)

 * Performance and bug fixes for WDQS
 * Service Level Objective (SLO) work for WDQS (T199228)
 * Carryover from Q1: continue to investigate Blazegraph support options and alternatives ✅

Status
October 29, 2018
 * The SLO work is a bit ❌, but still somewhat at this point due to varying conversations, but lots of work has been ongoing with the fixes on WDQS. The team is still investigating long term usage of Blazegraph and what that means to the Foundation.

November 29, 2018
 * This is now

December 13, 2018
 * These goals are still ; but the SLO work will flow into Q3. Blazegraph support options investigation is now ✅ and we are determining next steps.



=Q3 Goals =

Outcome 1 / Output 1
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Incorporate Natural Language Processing (NLP) in the machine learning analysis pipeline for search

Dependency: Will need some short-term consulting help during implementation

Tech Goal(s)

 * C: Improve our own feature set

Goal(s)

 * Work with NLP contractor on spelling and did-you-mean result tuning (T212884) and (T212888)
 * Complete Russian/English wrong keyboard detection (T138958)

Status
January 22, 2019
 * * The wrong keyboard detection work is ; the NLP contract work is ❌ for right now due to certain legal issues.

February 25, 2019
 * * The wrong keyboard work has been ❌ for now, as the NLP work has kicked off and is fully

March 2019

Outcome 1 / Output 2
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Better understanding of the effectiveness of our improvements to search and the performance of our tooling on the backend

Tech Goal(s)

 * C: Improve our own feature set

Goal(s)

 * Deploy improved autocomplete for English Entities
 * Use machine learning to improve autocomplete of Wikidata items for three more languages

Status
January 22, 2019
 * * The patch for this is ✅ and going out with this week's train and the A/B tests are going to be starting soon.

February 25, 2019
 * * Tested Spanish, English, and French - all good with the testing and is now deployed in production ✅

Outcome 1 / Output 3
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Improved support for multiple languages by researching and deploying new language analyzers where feasible on individual language wikis.

Tech Goal(s)

 * A: Foundation Goal: Reach
 * B: Serving our audiences
 * C: Improve our own feature set
 * D: Technical Debt

Goal(s)

 * Deploy Korean morphological library into production (after Elasticsearch is upgraded)
 * General language support (i.e, misc language-specific bugs)

Status
January 22, 2019
 * * We're still working on upgrading ElasticSearch, so the deployment of Korean library is still ❌ at this point. General lang support is and ongoing.

February 25, 2019
 * * The Korean update is and planned for next week to be rolled out as part of the ES6 upgrade. General lang support is  and ongoing.

March 2019

Outcome 2 / Output 1
Technical debt addressed and required maintenance completed for Search Platform components
 * Elasticsearch 6 upgrades and server replacements

Dependency: SRE, WMDE

Tech Goal(s)

 * C: Improve our own feature set
 * D: Technical Debt

Goal(s)

 * Upgrade ElasticSearch to v6
 * Complete separation of Wikidata ElasticSearch implementation into a separate extension
 * JVM and ElasticSearch upgrade Spicerack cookbooks
 * Stretch goal: Start working on the CloudElastic replicas (and perform a proof of concept with a few select wikis)

Status
January 22, 2019
 * * The upgrade is still and troubleshooting issues with cluster states and building a whole new big bunch of shards to handle the increased load.
 * * The separation of Wikidata ElasticSearch implementation is still, but other work is also on-going right at the moment.
 * * JVM and ES upgrade is ; we are doing first passes at the integration testing, and will have a first set of cookbooks soon.
 * * Stretch goal might be a bit closer than we initially thought, but once ES6 is in production, we can finish this up, maybe in mid February.

February 25, 2019
 * * ES6 is planned to be deployed the week of March 4th
 * * Wikidata ElasticSearch implementation is still and we hope to get it mostly done by end of this quarter, but might go over into next quarter for the deployment.
 * * JVM and ElasticSearch upgrade is still - ES6 cookbooks are ✅ and we only have a little bit to do with the rest of the WS6 upgrade. (T202885)
 * * Stretch goal is (T214921)

March 2019

Outcome 2 / Output 2
Technical debt addressed and required maintenance completed for Search Platform components
 * Higher capacity for WDQS to improve its ability to power features on-wiki for readers and the growing set of features for supporting structured data

Dependencies: SRE, WMDE

Tech Goal(s)

 * B: Serving our audiences
 * C: Improve our own feature set
 * D: Technical Debt

Goal(s)

 * Performance and bug fixes for WDQS
 * Service Level Objective (SLO) work for WDQS (T199228)
 * Release official Blazegraph code package and start using Blazegraph CI
 * Roadmap planning for WDQS

Status
January 22, 2019
 * * Perf / bug fixing is on-going and along with a new roadmap on how to figure out which ones come first.
 * * SLO is, we'll talk about it during All Hands week
 * * We are having issues with Blazegraph right now, but we're working them, so for the issues, but the official code package is

February 25, 2019
 * * Perf / bug fixing for WDQS is on-going and
 * * SLO work is in a waiting status for us, but we're keeping it
 * * Blazegraph's CI is still getting attention and is (T216855)

{to do}} March 2019



= Q4 Goals =

Outcome 1 / Output 1
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Incorporate Natural Language Processing (NLP) in the machine learning analysis pipeline for search

Dependency: Using short-term consulting help

Tech Goal(s)

 * C: Improve our own feature set

Goal(s)
Search "Local Impact":
 * Complete 'did you mean' (DYM) project with NLP contractor (T212884)
 * Assess performance and investigate beginning integration work for deployment
 * Enable new Korean analysis, reindex clusters, and retrain the 'learning to rank' (LTR) model (T216738)

Status
April 2019
 * Discussed...

May 2019
 * Discussed...

June 2019
 * Discussed...

Outcome 1 / Output 3
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Improved support for multiple languages by researching and deploying new language analyzers where feasible on individual language wikis.

Tech Goal(s)

 * A: Foundation Goal: Reach
 * B: Serving our audiences
 * C: Improve our own feature set
 * D: Technical Debt

Goal(s)

 * Search "Local Impact": making making bigger improvements for smaller (or underrepresented) communities T218613

Status
April 2019
 * Discussed...

May 2019
 * Discussed...

June 2019
 * Discussed...

Outcome/ output
Through incremental Search Platform component improvements, teams and developers can deliver more and better ways for readers and editors to search for content across languages.
 * Users across languages experience better search results.

Goal(s)

 * Investigate and continue to revise search metrics and dashboards (T216055)

Status
April 2019
 * Discussed...

May 2019
 * Discussed...

June 2019
 * Discussed...

Outcome 2 / Output 1
Technical debt addressed and required maintenance completed for Search Platform components
 * Elasticsearch 6 upgrades and server replacements

Dependency: SRE

Tech Goal(s)

 * C: Improve our own feature set
 * D: Technical Debt

Goal(s)

 * Adding ability for cloud environment to use ElasticSearch and perform a proof of concept with a few select wikis (T214921)

This work is often referred to as "Cloud Elastic Replicas".

Status
April 2019
 * There might be some work needed to do this month after the ES6 upgrade that should be finished in q3

May 2019
 * Discussed...

June 2019
 * Discussed...

Outcome 2 / Output 2
Technical debt addressed and required maintenance completed for Search Platform components
 * Higher capacity for WDQS to improve its ability to power features on-wiki for readers and the growing set of features for supporting structured data

Dependencies: SRE, WMDE

Tech Goal(s)

 * B: Serving our audiences
 * C: Improve our own feature set
 * D: Technical Debt

Goal(s)

 * Improve the performance and functionality of Blazegraph (the graph storage engine behind Wikidata Query Service).
 * Increase Blazegraph support for SPARQL operations. Example: T200612
 * Improve query performance of Blazegraph in areas of particular interest for WMF. Example: T152773

Status
April 2019
 * Discussed...

May 2019
 * Discussed...

June 2019
 * Discussed...