We prioritized metrics that people spoke up for on Analytics/Wikistats/DumpReports/Future per report. Breakdowns allow us to put different types of data under the same metric, for example very active and active editors are different categories of editors. If breakdowns are hard to understand, let us know.
Topic on Talk:Wikistats 2.0 Design Project/RequestforFeedback/Round1/Site architecture
Breakdown per country is not available. I am interested in keeping:
- most viewed / edited wikis for each country
- countries a wiki is most viewed / edited from.
Wikimedia Traffic Analysis Report - Wikipedia Page Views Per Country - Trends (1) had only one support, but it was intially forgotten and was added only in September when most users have already voted. It would be unfair to drop it.
Breakdown per country is definitely useful, as described by NickK. For wikis targeting a specific country, it is always useful to see where do people in that country go.
Same about breakdown per country - very interested in that! Otherwise, it's fine.
+1 to breakdown per country.
I would also like to see:
- downloads for media on Commons
- survival / rolling survival new active editors.
Breakdown per country / language reports are still operational Wikistats reports, and have already been updated to hadoop data stream. My understanding is that they are kept as is for now, and possibly migrated later.
https://stats.wikimedia.org/wikimedia/squids/SquidReportPageViewsPerCountryOverview.htm
https://stats.wikimedia.org/wikimedia/squids/SquidReportPageViewsPerCountryBreakdown.htm
https://stats.wikimedia.org/wikimedia/squids/SquidReportPageViewsPerLanguageBreakdown.htm
These are all page views reports. Whenever a similar hadoop based data stream appears for page edits I can revive those as well.
FYI: as for Trends report: I discontinued https://stats.wikimedia.org/wikimedia/squids/SquidReportPageViewsPerCountryTrends.htm because some of the Year over Year fluctuations seemed too large to be plausible. Hopefully with new hadoop data things will improve (1:1 instead of 1:1000 sampling makes a difference, especially for smaller countries). But some major anomalies could (and maybe can) be explained best by MaxMind database lagging behind reality (swaps of ip ranges between top level providers, without informing MaxMind).
I think there's a lot of interest in country-level information, so I definitely support including as much as we can within our privacy limitations.
I also think it would be great to see Wikistats include the editor model breakdowns of active editors by tenure; they add a lot of depth to the active editor numbers and are certainly more useful than newly registered users (since we care about new editors much more than new registrants who might have no interest in actually editing). On the other hand, this lineup of metrics is keeping pretty close to the existing Wikistats lineup, so I understand if you want to focus on getting the new design and architecture in place rather than on updating the metrics offered.
As a side note, what is "mean articles"?
We definitely focused on the editor model and things like "new editors" more as part of the back-end of wikistats, the Data Lake and upcoming edit metrics API. So we'll have the support for those and more metrics. As far as including those perspectives into wikistats, my hope is that a community will build around the new interface and approach and they'll have that conversation. I don't see it as our place to decide, except to create the infrastructure and make it easy to execute.
"mean articles" is a placeholder name for "edits this month / total articles". It's how wikistats refers to it, but we'll think of something better.
Wikistats knows of mean edits ("total edits over all time / total articles") and mean bytes. Not metrics that are often quoted, but trivial to calculate.