Extension:ORES

The ORES extension integrates data from an  service into the RecentChanges view.

Currently, the ORES backend service is only set up for Wikimedia wikis, and significant work would be required to set it up for third-party MediaWiki installations.

Installation
You need to run CheckModelVersions.php maintenance script once it's deployed (and after that you can run PopulateDatabase.php too)

If you want to setup a local development environment for MediaWiki + ORES extension using the following ORES extension local development guide :

Config variables
Here's the config variables and their default values and a little description about them.

ORES service responses
ORES extension is merely more than an interface to the ORES service. The service returns a probability score of edits being damaging like this (API v1):

It means this edit is 10% likely to have caused damage. Note that 90% likely doesn't mean 9 out of ten cases will be vandalism. Choosing thresholds should be done via analysing recall (percentage of vandalism it can catch) or false positive rate. In ORES the "soft" threshold is when recall is 75% (meaning it will include 75% of all damaging edits) and the "hard" threshold is when recall is 90%. You can get the thresholds from model info (an example).

Database schema
ORES extension introduces two new tables: ores_model and ores_classification. See the full database schema description.

Scores
Once an edit is made the extension triggers a job to hit the service and store the results in the ores_classification table. It means it will not include scores for edits made before the deployment. In order to fill the database you can run the maintenance script PopulateDatabase.php. It will hits the service and keeps the score for the last 5,000 edits. You can run it several times if needed.

Once a model gets updated to a newer version CheckModelVersions.php</tt> maintenance script needs to be ran to update the ores_model</tt> table which will cause to scores stored in the ores_classification</tt> table become deprecated. You can clean these obsolete scores by running PurgeScoreCache.php</tt> maintenance script.

Interface
The extension won't show anything when deployed but it will add itself as a beta feature ( is a dependency of this extension) and once it's enabled by the user it will use hooks in ChangesList (RecentChanges, Watchlist, and RelatedChanges) in both old and enhanced mode and highlights when score exceeds the given threshold.