Help:Extension:Translate/Statistics and reporting

Both for the translator, to know how to find things to do, and the project coordinators, to monitor what's going on; and to make visualizations of the wiki community/work for the outside.

Translate extension provides lots of statistics, most of them are updated in real time. These are exposed primarily through for special pages named LanguageStats, MessageGroupStats, TranslationStats and SupportedLanguages. The first two are different views to the same data: completion percentages of each language of each message groups. The latter two pages help translation admins to track the health of the translation community, both from high perspective and from close-up detail perspective.

Completion statistics for language
Primary audience is translators. Provided by Special:LanguageStats. This page is almost always set up to be the jumpboard for translators. They get overview of all message groups that are available and how much work each group still needs, to easily find what to work on.

Translation administrators can group message groups into larger groups, which makes them collapsible and expandable in the statistics table and helps translators who are interested only in some translation projects. If message group workflow states are used, they will also be shown on this page.

Completion statistics for message group
Primary audience is translation and project managers. Provided by Special:MessageGroupStats. This page gives an overview of translation level of a message group. It can be used to assess how many languages have adequate level of translation, which languages need messaging to reach the threshold by the deadline or what languages have just started. You can use this page together with list of languages and translators to find the translators of any language. If message group workflow states are used, they will also be shown on this page.

List of languages and translators
Primary audience is translation administrators. Provided by Special:SupportedLanguages. This is the translation administrator's high level overview of the translation community of the wiki. All used languages are listed there and their activity level is visualized by a tag cloud. Bigger text means more active language. There is also list of translations, annotated with how much work they have done and whether they have been inactive for some time. Translation administrator can use the list to find translators for urgent translation jobs or just to ping inactive translators to try to get them come back and be active again. Translators can also use it to find fellow translators in their language who are active and can be contacted, thus improving interaction and collaboration in the translation community.

Graphing the activity
Primary audience is translation administrators. Provided by Special:TranslationStats. This page acts both as a tool to inspect the community activity as well as generating nice graphs. The page is essentially a graph generator. You can choose to map any of the following three parameters (only at a time): number of active translations, number of translations edits or number of new user registrations. You can choose the time scale and period and the image size. You also get a wikitext that you can copy to any page you want to include the graph. The graphs are cached for few hours, but essentially they update in almost real time.

You can limit the graph to only certain message groups or to certain languages to make comparisons. Or you could make a graph of Finnish, Swedish, Norwedian, Danish and Iceland and show that in prominent place to cause some competition and boost translation activity.

The availability of this page depends on PHPlot being installed and configured.

Static translation statistics table
There are a couple of command line scripts that let you create custom version of tables shown in Special:MessageGroupStats. You can choose multiple groups and the list of languages. The scripts can produce output in different formats. If you want to keep these tables up to date you have to rerun the scripts regularly.

XXX

Recent changes
Primary audience is all users. Special:RecentChanges tracks all translation related work. Some filter are added to make it more useful, especially in the case of page translation where each edit is performed on the translation unit page and copied over the translation page, hence recorded two times.


 * "": don't filter anything, show complete feed.
 * "": shows only edits to all system messages, their translations and all translation namespaces.
 * "" is the default option: hide all the edits shown with the previous one.
 * "": show only edits to actual system messages used by the wiki interface (MediaWiki pages, not subpages).

Filters apply in the same way also to actions on such pages and also to their talk pages.

Translations in all languages
Todo: Documentation for Special:Translations.

XXX

Users rating
Primary audience is translators. Provided by Special:ContributionScores (added by Contribution Scores extension. This page produces a rank of users based on the number of edited pages and edits they have in the last 7 days, 30 days or all time. It's useful to see who's been most active on the wiki in the last few days and to compare your activity to the others'. Custom charts can be generated and included in any page, by passing parameters to the special pages in the subpage format, for instance:.
 * 1) First parameter is the number of users shown in each table.
 * 2) Second is the number of days to consider ( for all time).
 * 3) Third is list of configurations separated by comma:
 * 4) * hides the standard links to user talk, contributions etc. after each username;
 * 5) * makes the table not sortable.

only edits to translatable pages/translation pages/both are counted; the default can/can't be configured blabla [add]

Maps
Maps are a useful feature added by Semantic Maps extension. They're not specific to translation work, but they can be of use for instance in project and language portals/coordination pages, which are among the ../Translation best practices/. See for instance the map of MediaWiki translators on translatewiki.net.

Thanks to maps the distribution of translators in the physical world can be easily visualized, which means that: people from outside the community sew how it's vibrant and world-spread (as every translation community shall be); translators can feel this but also see where other translators working on the same language/project are, building a sense of community (and perhaps even making new friends); projects coordinators and wiki administrators can see also the geographies (not only the languages) where the wiki is doing well or could be improved.

Reporting features

 * logs
 * recent changes feeds