Totally! There are lots of really cool applications we can do with the API.
A couple of comments -- first, we need to establish what constitutes a page
view. We've done some work on this that we shared at FOSDEM and the next
step is to start discussions with the community.
I do need to say that a bulk query interface is probably the first thing
we'll build once we have the page views. A low-latency lookup system is a
little bit harder technically and will take a little longer. Definitely on
the radar though!
On Thu, Feb 20, 2014 at 11:30 AM, Ryan Kaldari <rkaldari(a)wikimedia.org>wrote;wrote:
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.
On Wed, Feb 19, 2014 at 3:14 PM, Toby Negrin <tnegrin(a)wikimedia.org>wrote;wrote:
Many of you have read Magnus' post on his
I've commented on his blog and I wanted to repost here and address Magnus'
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.
Analytics mailing list
Analytics mailing list