We are aiming to use testwiki as an introduction to Growth features (see parent task). It would be nice if those features could include ORES topics. If the articletopic model would be enabled on that wiki, I think the rest would just work (after a Cirrus refresh). The quality of predictions doesn't matter much, so the enwiki model could be reused.
If it's not much work, please enable it.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Goal | Trizek-WMF | T228980 [goal] Deploy Growth features on wikis requesting them | ||
| Open | Trizek-WMF | T247507 Scale: deploy Growth features to 100 wikis | |||
| Resolved | Trizek-WMF | T253254 Scale: add articles to test Wikipedia so that users can try SuggestedEdits | |||
| Resolved | Halfak | T257248 Add articletopic model to testwiki |
@Tgr -- which team would be doing this work? Is it Growth, Scoring, or Search? Or all three?
Aha! We don't have it here, but we could. See https://ores.wikimedia.org/v3/scores/testwiki/
I'm thinking that we would just re-apply the enwiki topic model in testwiki.
This is work for the Scoring team (a simple configuration change, hopefully).
I'm not 100% sure if the Search part of the pipeline would work out automagically, but I think it would.
That would be ideal, the text of the articles is taken from enwiki so it would probably give reasonable predictions. Although even if it doesn't, having the topic filter feature available would be a plus, even if the results are random.
Thanks for helping on this, @Halfak. Is this something you can easily knock out, or should we plan it for later?
@EBernhardson @dcausse -- do you know if the pipeline part would just work?
For the elastic update pipeline, once mediawiki starts reporting scores for testwiki to mediawiki_revision_score events, and the ores api reports testwiki as having the appropriate model (for fetching thresholds), then everything else should "just work". If we want to populate the full set of pages, rather then only the ones with revisions after the deployment date there is a small amount of work to do, but it shouldn't be too complex.
Change 610851 had a related patch set uploaded (by Halfak; owner: Halfak):
[mediawiki/services/ores/deploy@master] Adds drafttopic and articletopic models for testwiki
Thanks, @Halfak!
Yes, @EBernhardson, we will want to score pages with revisions before the deployment (the pages that already existed on Test Wikipedia).
Change 614834 had a related patch set uploaded (by Halfak; owner: Halfak):
[mediawiki/services/ores/deploy@master] Adds draft/articletopic models to testwiki
Change 610851 abandoned by Halfak:
[mediawiki/services/ores/deploy@master] Adds drafttopic and articletopic models for testwiki
Reason:
Change 614834 merged by Calbon:
[mediawiki/services/ores/deploy@master] Adds draft/articletopic models to testwiki
This doesn't seem to be working, selecting a topic on test.wikipedia.org/wiki/Special:Homepage results in no results, no matter what topic is added.
Putting this in our current sprint so we could have a look about where things are breaking down.
Searching by topic does seem to work, so I think the task as stated is resolved.
I assume existing articles have not been scored, so we'd have to make a bunch of dummy edits to index them.
I'll run the process to bulk score and import articletopic for testwiki. Shouldn't take too long, testwiki is pretty small.