Page MenuHomePhabricator

Reconsider how stub articles are selected for Expand article Suggested edit
Open, Needs TriagePublic

Description

Problem
At the moment, Suggested edits are based on templates. However, some wikis has a low number of articles connected to stub templates, if not no templates at all (case of smaller wikis). Hence, newcomers can't find articles to edit.

Possible solution
The idea would be to stop using templates, and go with a query. During the Growth Ambassadors meeting, the idea came from this query:

pages that are in namespace 0 AND are not redirects AND are less than 1500 characters/bytes long

Configuration
Communities may be okay to keep templates, but some other might appreciate to have a simple, more automatic way to select stubs. In community configuration, the idea would be to select between templates (as exists) or query, and, for the query, to select the number of bytes (1500 could be the default).

Event Timeline

@Trizek-WMF @KStoller-WMF @MShilova_WMF is there an epic task that this would fit well with?

As for the query: we don't currently have a way to easily incorporate streams of potential edits unless they can be found via Special:Search. So, if we want to do something with character length, we'd have to get Discovery-Search to implement some kind of charlengthlesesthan:1500 keyword (probably not that difficult?), or, we need to rework how we can get other sources of data into suggested edits feed (harder).

@kostajh , we don't have any relevant active epic at the moment that this task can potentially align with.

@MPhamWMF please let us know if adding some kind of charlengthlesesthan:1500 keyword (or other way to search by article size) is a change that you think makes sense and is something the Search Platform team is able to take on.

If not, I think this is a nice idea, but likely too high effort to rework how we pull data into the suggested edits feed.

@KStoller-WMF , I don't think implementing something like this should be too much work for the Search team, and we can aim to get it done this quarter. We created a separate ticket to track it (https://phabricator.wikimedia.org/T328332), as this ticket seems a little bit broader than just implementing a keyword. We'll untag ourselves from this ticket, but let me know if anything else relevant comes up.

@KStoller-WMF @Trizek-WMF T328332: Add a new keyword to filter pages based on their "length" should be in group2 later today. The next step is for us to integrate the ability to filter candidate articles based on the new search term, textbytes. T328332 documents what the options are:

The keyword will be usable the same way as other numeric keyword we support File measure.

  • comparison: textbytes:<1500 or textbytes:>1500 all pages with text_bytes greater and lesser than 1500
  • ranges: textbytes:1500,10000 all pages with text_bytes between 1500 and 10000
  • exact match are possible but probably useless, e.g. textbytes:10

I think it is probably most straightforward to expose a new option for all task types that allows communities to use textbytes for comparison or ranges, and that would get saved in MediaWiki:NewcomerTasks.json as a new field.

so e.g. communities could also decide that "copyedit" task should only include articles with textbytes:>500; this doesn't have to just be about the "Expand" task type.

What do you think?