Statistics page

Issue #101 resolved
Ivo Kruusamägi created an issue

http://mwtranslate2.keeleleek.ee/

Page should include note, that users can op-out from sending their translation information and therefor it is possible that more edits have been made than what is shown in this page.

"Most used wikis" red bubbles are problematic. They show only 6 out of 13 languages (some notable language versions are missing; for example --> olo). They aren't arranged by size, but they out to be.

Link to raw data (http://mwtranslate2.keeleleek.ee/all) should be added + link to page, that will explain what can be seen in that JSON file.

"Usage over time" needs some updating and fixes.

Comments (5)

  1. Kristian K

    Proposal 1: "Notice that users are free to choose if they want to contribute to the statistics or not, thus the information here can not be used as proper usage statistics of the tool."

    Proposal 2: instead of "Most used wikis" could be "Contributed Wikipedia language editions" and have all languages shown with sized balls (ask me if unsure how to format it all).

    Proposal 3: text for the raw data link: "Download the full statistics as JSON. Read [more about what it contains]." (the link could be to here http://translate.keeleleek.ee/wiki/Corpus I will edit the text later)

    Proposal 4: Instead of "Usage over time" could be "Edits in the last two years". (and thus have the svg be dynamically generated with info of the last 24 months)

  2. Kristian K

    Proposal 5: The search form Instead of "Records" could be "Search" or "Search statistics" Instead of "Username" could be "Title" (change the search logic accordingly) Instead of "Tag" could be "Tagged with" or "Has tag" Instead of "Exact" could be "Marked as exact" Instead of "Go" could be "Show" or "Find" or "Search"

    In the results table: Change "Source" to "Used articles" Change "Title" to "Article title"

  3. Andrjus Frantskjavitsius repo owner

    This should be done.

    Some proposals were not implemented. If you feel that something was left out, please create a new issue.

  4. Log in to comment