- [[ https://meta.wikimedia.org/wiki/Schema:TranslationRecommendationUserAction | TranslationRecommendationUserAction ]]
- [[ https://meta.wikimedia.org/wiki/Schema:TranslationRecommendationUIRequests | TranslationRecommendationUIRequests ]]
- [[ https://meta.wikimedia.org/wiki/Schema:TranslationRecommendationAPIRequests | TranslationRecommendationAPIRequests ]]
See: https://wikitech.wikimedia.org/wiki/Event_Platform/EventLogging_legacy
We will keep client_ip and geocoded data for these schemas.
---
=== Recommendation API code changes needed
Since these events are sent to the legacy eventlogging backend using from a custom client (not via the MW EventLogging extension), the code will need to be changed to send events to EventGate instead.
It looks as though this code has both [[ https://github.com/wikimedia/research-recommendation-api/blob/0d25420f747dab2a25b1a58c358306bf50ebd7de/recommendation/web/static/event_logger.js | JavaScript ]] and [[ https://github.com/wikimedia/research-recommendation-api/blob/0d25420f747dab2a25b1a58c358306bf50ebd7de/recommendation/utils/event_logger.py | Python ]] logic to send events. Both implementations will need updating to send events to EventGate.
For more info see:
- https://wikitech.wikimedia.org/wiki/Event_Platform/EventGate
- https://wikitech.wikimedia.org/wiki/Event_Platform/Stream_Configuration
- https://intake-analytics.wikimedia.org/?doc#/default