Deputy/Research

From Meta, a Wikimedia project coordination wiki
Deputy
Copyright cleanup and case processing tool for Wikipedia
Development is a constant cycle of seeing what works and what doesn't. To know what works, we have to take a look at how Deputy is used, and what editors think of Deputy. This is where research for the tool comes in.

Research allows for a comprehensive look at Deputy's performance, based primarily on the following key questions:

  1. Does it work? (bug-free, stable)
  2. Is it helpful? (friendly interface, problem-free edits)
  3. Is it effective? (saves time, easier than manual work)

When these goals aren't met or when there's room for improvement, development shifts accordingly. The main priority is to have an effective tool that users want to use; not one that users may feel forced to use, either because it disrupts manual work or it's at least something other than manual work.

Reports

Reports are the primary resource in research for Deputy. These are records and analyses of collected data, and decide the direction of the project in the long-term.

The following reports for Deputy have been published in the past:

Surveys
Main article: Deputy/Research/Surveys

Occasionally, there will be surveys that will attempt to gauge Deputy's effectivity on the projects. These surveys gauge user experience, satisfaction, and retention.

The following surveys have been run in the past:

Queries

A lot of Wikimedia data is available to the public through Quarry. This includes revision information, pages, users, log events, and the like. Using publicly-available data, we can infer how Deputy performs as a tool, how frequent it gets used, and on what pages it is used on the most.

The following queries exist for Deputy: