**May 25 - May 29**
- Had meeting with Nikerabbit and Nemo_bis to discuss mainly T98665
- Work in progress for T100175 (reuse TUX elements)
- Investigating better approach to display translated and untranslated messages:
# Fetch all resultset at once without size parameter: Easy for displaying translated messages. May prove to be inefficient as documents grow. We may get result within 1st 100 resultset or so, then fetching remaining resultsets is not useful.
# Fetch 100 results(apply size parameter), if a minimum no. of translations(i.e. 25) are not found then search for next 100 and so on: Will not make unnecessary fetch but may require quite number of search iterations in the worst case.
# Third approach [[ https://www.elastic.co/guide/en/elasticsearch/guide/current/denormalization.html | Data Denormalization ]] better than the above two: Add new field to documents for list of languages for which translations exist. We can use the same field as missing query for finding untranslated messages. This would also require code changes for translations update.
- As per discussion, review in progress for submitted patch T97961.
- Sorted the group list based on search result count instead of alphabetically T100393
- Identified the problem for messages groups not listed from different wikis T100648. Need discussion for any possible solution for the same.
**June 1 - June 5**
- [[ https://gerrit.wikimedia.org/r/#/c/216958/ | Added support for translated and untranslated messages in Special:SearchTranslations
]]. Though this process was efficient but due to space consumption by indexing extra translated and untranslated language codes for each message, this process for now would not be an option.
We should try to use MessageCollection if we could not come up with any better approach.
**June 8 - June 12**
- The above mentioned procedure would require update of more than 300 documents for a translation, in comparison to one document update.
- https://gerrit.wikimedia.org/r/#/c/217239/
- Discussion with the mentors for a better solution: If we are unable to retrieve the required results with ES indexed documents, then we may at last use MessageCollection( which requires db hit ) to collect data.
- Algorithm currently working on to filter out translated and untranslated messages( no extra fields are required ):
-- Use "Filtered query" to search for a string in a source language and collect 'localid' and 'scores'( keep scores for documents to not lose its relevance )
-- Find translated messages from the list of 'localid' and use Function score script to replace the scores of the documents returned with the scores from step 1.
-- The list of id's from step 2 not found in the list from step 1 are the untranslated messages.
-- Here the fuzzy messages are counted in untranslated messages because currently we do not keep the indexed documents for fuzzy messages. So to keep track for fuzzy messages we have to filter out messages from untranslated messages retrieved in step 3. We can achieve this by using MessageCollection->filterFuzzy(). The main problem lies in efficiency to retrieve fuzzy messages which involves steps 1->2->3.
--- I think what might work is to keep fuzzy messages instead of deleting it from the index and to help us filter out fuzzy messages from translated ones, add a extra field fuzzy with no data.( If we are totally against adding an extra field due to space constraint, we may try using different format for localid , e.g. fuzzy-MediaWiki:Config, though not sure as it may break some functionality )
**June 15 - June 21**
- Read documentation for MessageCollection and its usage.
- submitted patch to support cross language search to display translated messages using MessageCollection https://gerrit.wikimedia.org/r/#/c/218859/
**June 22 - June 28**
- API for search translations T100176
- Allow wildcard search T100345
- Support for untranslated messages using MessageCollection https://gerrit.wikimedia.org/r/#/c/220447/
- Investigating parent/child mapping to find a better way to index related documents and to provide an user friendly faceted navigation.
**June 29 - July 3**
- Midterm evaluation
- Integrate search features
- Deploy code in Labs-instance
- User Interface enhancements.
- Reading elasticsearch documents.
**June 4 - July 10**
- Updated patch to include URL parameter 'sourcelanguage'.
- Advertised Search Translations T105140
- Toggle group filter.
- Allow search for messages that contain all the words of the search string, i.e., AND operator.
- Designed a mockup to provide an interface for different search parameters.