Extension:ORES/uk

Розширення ORES інтегрує дані зі сервісу до розрізу «Нещодавні зміни».

Наразі, задній сервіс ORES встановлено лише для вікі Вікімедіа, тоді як його встановлення для сторонніх інсталяцій MediaWiki потребує значної кількості роботи.

It is installed on several Wikimedia sites, but no longer deployed to new ones. For newer work on machine learning in Wikimedia, see.

Встановлення
Після розгортання слід виконати сценарій обслуговування CheckModelVersions.php (після чого можна виконати й PopulateDatabase.php)

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



Конфігураційні змінні
Тут — конфігураційні змінні, їхні значення за замовчуванням і малий опис про них.



Відповіді сервісу ORES
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).



Схема бази даних
ORES extension introduces two new tables: ores_model and ores_classification. See the full database schema description.



Рахунки
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 maintenance script needs to be ran to update the ores_model 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.

Інтерфейс
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.