I also want to call out that the Analytics team has been supporting a wide range of users and stakeholders during the year. We've developed WikiMetrics, a tool for measuring editor productivity that is used by WMF program evaluation and community members; provided dashboards and support for Wikipedia Zero, our program to partner with our mobile partners to enable mobile Wikipedia access free from data charges; and supported product teams and researchers both inside and outside of the foundation.

Hi Everyone, Many of you have read Magnus' post on his blog<http://magnusmanske.de/wordpress/?p=173>. I've commented on his blog and I wanted to repost here and address Magnus' concerns directly. First of all, I'm sorry that we let Magnus and other folks down on the page view APIs -- we made some commitments late last year that we weren't able to meet. Not only that, these failures echoed previous points of frustration with the Foundation. I do want to note that we actively support the infrastructure that feeds data to stats.grok.se. We've fixed a number of issues with that pipeline, most recently last week. We understand the importance of this data to the community. The page view API project has been challenging for a number of reasons -- the size of the data, the fact that definitions of page views have not been updated to stay in line with the changing traffic (mobile, bots, API requests, etc) and the challenges in aggregating various aliases. We've needed to revisit our definitions of page views in order to get this right as well as design and build a global architecture for collecting these and other metrics. In addition, we've tried to do this with a perspective of privacy and respect for our users. To this end, we presented an approach to measuring page views in MediaWiki at FOSDEM in January and have made progress towards our new infrastructure by deploying middleware delivering unsampled page view data from mobile devices from our globally distributed datacenters to our compute cluster for analysis. However, these initiatives are complex and will take several months to complete at the earliest. In the meantime, we're working with Henrik to scale up stats.grok.se. I also want to call out that the Analytics team has been supporting a wide range of users and stakeholders during the year. We've developed WikiMetrics, a tool for measuring editor productivity that is used by WMF program evaluation and community members; provided dashboards and support for Wikipedia Zero, our program to partner with our mobile partners to enable mobile Wikipedia access free from data charges; and supported product teams and researchers both inside and outside of the foundation. We've been prioritizing and working on these projects as our resources allow and it's important to understand that the team has not been idle. While we've done a less than stellar job in communicating our progress to the community, information on what we've been doing is available via our planning pages <https://www.mediawiki.org/wiki/Analytics/Prioritization_Planning> on mediawiki. In the future, we will be more proactive in communicating with the community regarding our goals and projects. -Toby _______________________________________________ Analytics mailing list Analytics(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics

Your mileage may vary, but my good friend Hannes Mühleisen over at CWI Amsterdam maintains this tool: http://wikistats.ins.cwi.nl/. You can script it like so: http://wikistats.ins.cwi.nl/export.php?page=Lady_Gaga%7CBritney_Spears&… . I let Hannes have the final word, but it seems it is not steadily updating. Could it? Best, Tom -- Thomas Steiner, Employee, Google Inc. http://blog.tomayac.com, http://twitter.com/tomayac _______________________________________________ Analytics mailing list Analytics(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics

Hi Everyone, Many of you have read Magnus' post on his blog<http://magnusmanske.de/wordpress/?p=173>. I've commented on his blog and I wanted to repost here and address Magnus' concerns directly. First of all, I'm sorry that we let Magnus and other folks down on the page view APIs -- we made some commitments late last year that we weren't able to meet. Not only that, these failures echoed previous points of frustration with the Foundation. I do want to note that we actively support the infrastructure that feeds data to stats.grok.se. We've fixed a number of issues with that pipeline, most recently last week. We understand the importance of this data to the community. The page view API project has been challenging for a number of reasons -- the size of the data, the fact that definitions of page views have not been updated to stay in line with the changing traffic (mobile, bots, API requests, etc) and the challenges in aggregating various aliases. We've needed to revisit our definitions of page views in order to get this right as well as design and build a global architecture for collecting these and other metrics. In addition, we've tried to do this with a perspective of privacy and respect for our users. To this end, we presented an approach to measuring page views in MediaWiki at FOSDEM in January and have made progress towards our new infrastructure by deploying middleware delivering unsampled page view data from mobile devices from our globally distributed datacenters to our compute cluster for analysis. However, these initiatives are complex and will take several months to complete at the earliest. In the meantime, we're working with Henrik to scale up stats.grok.se. I also want to call out that the Analytics team has been supporting a wide range of users and stakeholders during the year. We've developed WikiMetrics, a tool for measuring editor productivity that is used by WMF program evaluation and community members; provided dashboards and support for Wikipedia Zero, our program to partner with our mobile partners to enable mobile Wikipedia access free from data charges; and supported product teams and researchers both inside and outside of the foundation. We've been prioritizing and working on these projects as our resources allow and it's important to understand that the team has not been idle. While we've done a less than stellar job in communicating our progress to the community, information on what we've been doing is available via our planning pages <https://www.mediawiki.org/wiki/Analytics/Prioritization_Planning> on mediawiki. In the future, we will be more proactive in communicating with the community regarding our goals and projects. -Toby _______________________________________________ Analytics mailing list Analytics(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics

Thanks for the update Toby! As far as prioritization of a Pageview API, this would be a hugely useful tool for the mobile team. Literally just yesterday I had to tell one of the designers that we couldn't implement the feature they wanted because we didn't have a Pageview API. Such an API would open up a world of new feature possibilities, many of which would be useful at promoting editor engagement. I'm sure you have a lot of other concerns to balance with such requests, but just wanted to throw in 2 cents from the mobile team. Cheers, Ryan Kaldari On Wed, Feb 19, 2014 at 3:14 PM, Toby Negrin &lt;tnegrin(a)wikimedia.org&gt;wrote;wrote: _______________________________________________ Analytics mailing list Analytics(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics