Edit Review Improvements/New filters for edit review/fr

La page Special:Recent Changes est un point de départ central pour beaucoup de types de révision des contributions. L'équipe Collaboration prévoit un ensemble de nouveaux outils — accessibles dans un premier temps en tant qu'option expérimentale — conçus pour améliorer la révision des contributions sur la page RC. Si elles sont efficaces, ces améliorations seront probablement généralisées sur la liste de suivi et d'autres pages de révision.

Parmi les nouveaux outils et les améliorations figurent notamment un ensemble de filtres prédictifs, basés sur le logiciel d'apprentissage automatique ORES (sur les wikis où ces prédictions sont disponibles), et une nouvelle interface qui améliore à la fois l'expérience utilisateur et l'efficacité de la recherche.

Ces améliorations aideront tous les relecteurs à mieux cibler leurs efforts et à être plus efficaces. Elles peuvent aussi potentiellement être bénéfiques pour les nouveaux contributeurs, qui ont besoin de plus d'accompagnement dans le processus de modification/relecture, d'après des résultats de recherches. Pour cela, elles exploiteront l'intelligence artificielle et d'autres moyens de trouver des modifications faites par des contributeurs qui a) sont nouveaux et b) font des erreurs mais c) de bonne foi (un objectif-clé des améliorations de la révision des contributions).

Those changes will also impact Special:RecentChangesLinked. Discover this new feature by visiting the Quick Tour page.

Améliorations, phase 1


Phase One RC page changes, available on all wikis as a Beta feature, include the following new capabilities and improvements:

Prédiction de la qualité des contributions
By enabling users to filter for good-quality edits, these filters empower reviewers who are, for example, looking to thank contributors; by helping detect bad-quality edits, they make numerous types of edit-review more efficient. The quality predictions are made by ORES, a machine learning service trained on a large set of edits previously scored by human editors.

Filters with different levels of accuracy are provided (ranging from "Very likely have problems" to "May have problems"). Stricter, more accurate filters find fewer false positives but return fewer results overall and so miss more of their target. Less accurate filters cast a wider net and find more of their target, but they also find proportionally more false positives. En savoir plus à propos des prédictions.

Prédictions de l'intention des utilisateurs
By enabling users to filter for edits made in good-faith, these filters empower reviewers seeking to support good-faith users; by enabling detection of bad-faith edits, they assist reviewers looking for vandalism. Like the Quality filters above, these predictions are made by the machine-learning service ORES. Also as above, filters at different levels of accuracy are provided to meet different users' needs. En savoir plus à propos des prédictions.

Filtres de niveau d'expérience
Research shows that new editors are particularly vulnerable to rejection. The Experience level filters enable reviewers to treat new users with the care they require and to identify contributions by users at a couple of more advanced levels. These are the Experience level filters:


 * : moins de 10 éditions et de 4 jours d’activité.
 * : plus de jours d’activité et d’éditions que les « », mais moins que les «  » (correspond au statut autoconfirmé).
 * : plus de 30 jours d’activité et 500 éditions (correspond au statut extended confirmed de la Wikipédia anglophone).

The filters return the edits only of users who are currently logged in.

En savoir plus à propos du filtrage.

Filtrage plus puissant
Most previous RC page filters offered only a simple option to show or hide a certain property (X). By augmenting these filters so that they now let users show or hide both X and its opposite (notX), the current tools provide more control. For example, previously, one could show Wikidata edits or hide Wikidata edits, but one could not show only Wikidata edits.

Furthermore, by organizing filters into logical groups, the new arrangement provides an improved ability to narrow results. (Logically, the new arrangement provides groups of OR filters, with each group of ORs being connected to other groups by ANDs.) En savoir plus à propos du filtrage.

Highlighting function
Among the many user interface improvements included in this project is a user-controllable highlighting function. By letting reviewers apply color to emphasize desired edit properties in the results area, Highlighting makes Recent Changes search results more meaningful. Among other user benefits, this new interpretive layer adds another tool for prioritizing work. Learn more about highlighting functions.

Au-delà de la phase 1
Once the Beta features described above are in place, we will gather user input and test satisfaction, then finalize plans for more improvements. The following options are under consideration:

Étendre la nouvelle fonctionnalité à plus de pages
Add the new filters and improved filtering interface to Watchlist, User contributions, Related changes and other, similar pages.

“Recently used filters”
By enabling the system to remember reviewers’ recent filter settings, help users to repeat their most common tasks quickly and easily, without having to input settings each time.

Upgrade interface and capabilities for the untouched RC page features
Phase one changes won’t affect all tools on the RC page. The following tools will remain unchanged: Namespace filters, Tag filters, filters for time frame, and number of results. Future efforts will likely bring these tools up to the new UI standard. This will enable the selection of multiple namespaces, multiple tag filters, and more specific time-frames.

Support ORES for propagated Wikidata edits
ORES supports Wikidata. You can enable it on wikidata.org and use it on Wikidata' Special:RecentChanges. The ORES extension doesn't currently handle these edits on the client-side (e.g. when viewing Wikidata changes relevant to any Wikipedia in Wikipedia RecentChanges page). We plan to fix it.

Deployment by default
The deployment by default is not scheduled yet.