The Language Team wants improvements to the content translation recommendation system.
This is the epic for the ML team for this task.
Description
Description
Event Timeline
Comment Actions
@calbon @kevinbazira should we keep this task open? If so, what are the next steps and/or subtasks?
Comment Actions
We are working on T338471 to figure out if the old recommendation-api service can be deprecated.
Comment Actions
hey all (not sure who exactly to tag but maybe I'll start with @kevinbazira just because I know you did a lot of good work on this) -- I'm working on some planning for improvements to our recommender systems for next fiscal year around what topic filters we provide to editors. Content Translation is of special interest but Android's SuggestedEdits is important too. The recommendation logic for both of these systems is still hosted on GapFinder as far as I can tell, but deploying any improvements is going to require moving them to a proper service (LiftWing). Does anyone know why this effort to move Content Translation's recommendation API over to LiftWing (along with Android's endpoints T340854) stalled last year?
Comment Actions
Hi @Isaac thank you for following up on this. The Content Translation recommendation API is now live in LiftWing production. It can be accessed through:
1.External endpoint:
curl -s "https://api.wikimedia.org/service/lw/recommendation/v1/api?s=en&t=fr&n=3&article=Apple"
2.Internal endpoint:
curl "https://recommendation-api-ng.discovery.wmnet:31443/api?s=en&t=fr&n=3&article=Apple"
Feel free to explore these endpoints, and if you encounter any edge cases, please don't hesitate to let us know. :)
Comment Actions
Ahh this is great news @kevinbazira ! @KartikMistry is there any reason from the Content Translation side why we can't switch over to the LiftWing endpoint? My read is that the code is quite simple -- e.g., if I go to Content Translation on Spanish Wikipedia, the tool hits this endpoint:
https://recommend.wmflabs.org/types/translation/v1/articles?source=en&target=es&seed=Music%20Modernization%20Act|Felony%20disenfranchisement&search=morelike&application=CX
To switch to LiftWing, the client would instead have to hit:
https://api.wikimedia.org/service/lw/recommendation/v1/api?s=en&t=es&article=Music%20Modernization%20Act|Felony%20disenfranchisement&search=morelike&application=CX
So just a change of base URL and I think a few parameters will have to change names too but the result is in the exact same format and will return the exact same results (so no change from the UI side yet needed).