Dear Data Enthusiasts,
In collaboration with the Services team, the analytics team wishes to announce a public Pageview API https://wikimedia.org/api/rest_v1/?doc#!/Pageviews_data/get_metrics_pageviews_per_article_project_access_agent_article_granularity_start_end. For an example of what kind of UIs someone could build with it, check out this excellent demo http://analytics.wmflabs.org/demo/pageview-api (code) https://gist.github.com/marcelrf/49738d14116fd547fe6d#file-article-comparison-html .
The API can tell you how many times a wiki article or project is viewed over a certain period. You can break that down by views from web crawlers or humans, and by desktop, mobile site, or mobile app. And you can find the 1000 most viewed articles https://wikimedia.org/api/rest_v1/metrics/pageviews/top/es.wikipedia/all-access/2015/11/11 on any project, on any given day or month that we have data for. We currently have data back through October and we will be able to go back to May 2015 when the loading jobs are all done. For more information, take a look at the user docs https://wikitech.wikimedia.org/wiki/Analytics/AQS/Pageview_API.
After many requests from the community, we were really happy to finally make this our top priority and get it done. Huge thanks to Gabriel, Marko, Petr, and Eric from Services, Alexandros and all of Ops really, Henrik for maintaining stats.grok, and, of course, the many community members who have been so patient with us all this time.
The Research team’s Article Recommender tool http://recommend.wmflabs.org/ already uses the API to rank pages and determine relative importance. Wiki Education Foundation’s dashboard https://dashboard.wikiedu.org/ is going to be using it to count how many times an article has been viewed since a student edited it. And there are other grand plans for this data like “article finder”, which will find low-rated articles with a lot of pageviews; this can be used by editors looking for high-impact work. Join the fun, we’re happy to help get you started and listen to your ideas. Also, if you find bugs or want to suggest improvements, please create a task in Phabricator and tag it with #Analytics-Backlog https://phabricator.wikimedia.org/tag/analytics-backlog/.
So what’s next? We can think of too many directions to go into, for pageview data and Wikimedia project data, in general. We need to work with you to make a great plan for the next few quarters. Please chime in here https://phabricator.wikimedia.org/T112956 with your needs.
Team Analytics
On 16 November 2015 at 13:50, Dan Andreescu dandreescu@wikimedia.org wrote:
Dear Data Enthusiasts,
In collaboration with the Services team, the analytics team wishes to announce a public Pageview API https://wikimedia.org/api/rest_v1/?doc#!/Pageviews_data/get_metrics_pageviews_per_article_project_access_agent_article_granularity_start_end. For an example of what kind of UIs someone could build with it, check out this excellent demo http://analytics.wmflabs.org/demo/pageview-api (code) https://gist.github.com/marcelrf/49738d14116fd547fe6d#file-article-comparison-html .
This is great to see. Thank you everyone for your work on this.
Yours,
This is fantastic news - thank you so much, Analytics, Services, Ops, and the communities who supported/requested this!
On Mon, Nov 16, 2015 at 1:50 PM, Dan Andreescu dandreescu@wikimedia.org wrote:
Dear Data Enthusiasts,
In collaboration with the Services team, the analytics team wishes to announce a public Pageview API https://wikimedia.org/api/rest_v1/?doc#!/Pageviews_data/get_metrics_pageviews_per_article_project_access_agent_article_granularity_start_end. For an example of what kind of UIs someone could build with it, check out this excellent demo http://analytics.wmflabs.org/demo/pageview-api (code) https://gist.github.com/marcelrf/49738d14116fd547fe6d#file-article-comparison-html .
The API can tell you how many times a wiki article or project is viewed over a certain period. You can break that down by views from web crawlers or humans, and by desktop, mobile site, or mobile app. And you can find the 1000 most viewed articles https://wikimedia.org/api/rest_v1/metrics/pageviews/top/es.wikipedia/all-access/2015/11/11 on any project, on any given day or month that we have data for. We currently have data back through October and we will be able to go back to May 2015 when the loading jobs are all done. For more information, take a look at the user docs https://wikitech.wikimedia.org/wiki/Analytics/AQS/Pageview_API.
After many requests from the community, we were really happy to finally make this our top priority and get it done. Huge thanks to Gabriel, Marko, Petr, and Eric from Services, Alexandros and all of Ops really, Henrik for maintaining stats.grok, and, of course, the many community members who have been so patient with us all this time.
The Research team’s Article Recommender tool http://recommend.wmflabs.org/ already uses the API to rank pages and determine relative importance. Wiki Education Foundation’s dashboard https://dashboard.wikiedu.org/ is going to be using it to count how many times an article has been viewed since a student edited it. And there are other grand plans for this data like “article finder”, which will find low-rated articles with a lot of pageviews; this can be used by editors looking for high-impact work. Join the fun, we’re happy to help get you started and listen to your ideas. Also, if you find bugs or want to suggest improvements, please create a task in Phabricator and tag it with #Analytics-Backlog https://phabricator.wikimedia.org/tag/analytics-backlog/.
So what’s next? We can think of too many directions to go into, for pageview data and Wikimedia project data, in general. We need to work with you to make a great plan for the next few quarters. Please chime in here https://phabricator.wikimedia.org/T112956 with your needs.
Team Analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Awesome !! And once more a thank you to Henrik who selflessly maintained his stats.grok.se for so many years !!!
DJ
On 17 nov. 2015, at 04:40, Rachel diCerbo rdicerb@wikimedia.org wrote:
This is fantastic news - thank you so much, Analytics, Services, Ops, and the communities who supported/requested this!
On Mon, Nov 16, 2015 at 1:50 PM, Dan Andreescu <dandreescu@wikimedia.org mailto:dandreescu@wikimedia.org> wrote:
Dear Data Enthusiasts,
In collaboration with the Services team, the analytics team wishes to announce a public Pageview API https://wikimedia.org/api/rest_v1/?doc#!/Pageviews_data/get_metrics_pageviews_per_article_project_access_agent_article_granularity_start_end. For an example of what kind of UIs someone could build with it, check out this excellent demo http://analytics.wmflabs.org/demo/pageview-api (code) https://gist.github.com/marcelrf/49738d14116fd547fe6d#file-article-comparison-html .
The API can tell you how many times a wiki article or project is viewed over a certain period. You can break that down by views from web crawlers or humans, and by desktop, mobile site, or mobile app. And you can find the 1000 most viewed articles https://wikimedia.org/api/rest_v1/metrics/pageviews/top/es.wikipedia/all-access/2015/11/11 on any project, on any given day or month that we have data for. We currently have data back through October and we will be able to go back to May 2015 when the loading jobs are all done. For more information, take a look at the user docs https://wikitech.wikimedia.org/wiki/Analytics/AQS/Pageview_API.
After many requests from the community, we were really happy to finally make this our top priority and get it done. Huge thanks to Gabriel, Marko, Petr, and Eric from Services, Alexandros and all of Ops really, Henrik for maintaining stats.grok, and, of course, the many community members who have been so patient with us all this time.
The Research team’s Article Recommender tool http://recommend.wmflabs.org/ already uses the API to rank pages and determine relative importance. Wiki Education Foundation’s dashboard https://dashboard.wikiedu.org/ is going to be using it to count how many times an article has been viewed since a student edited it. And there are other grand plans for this data like “article finder”, which will find low-rated articles with a lot of pageviews; this can be used by editors looking for high-impact work. Join the fun, we’re happy to help get you started and listen to your ideas. Also, if you find bugs or want to suggest improvements, please create a task in Phabricator and tag it with #Analytics-Backlog https://phabricator.wikimedia.org/tag/analytics-backlog/.
So what’s next? We can think of too many directions to go into, for pageview data and Wikimedia project data, in general. We need to work with you to make a great plan for the next few quarters. Please chime in here https://phabricator.wikimedia.org/T112956 with your needs.
Team Analytics
Analytics mailing list Analytics@lists.wikimedia.org mailto:Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics https://lists.wikimedia.org/mailman/listinfo/analytics
--
Rachel diCerbo Director of Community Engagement (Product) Wikimedia Foundation Rdicerb (WMF) <https://meta.wikimedia.org/wiki/User_talk:Rdicerb_%28WMF%29 https://meta.wikimedia.org/wiki/User_talk:Rdicerb_%28WMF%29> @a_rachel <https://twitter.com/a_rachel https://twitter.com/a_rachel> _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org mailto:Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Grah, too early in the morning.... unselfishly of course !!!
DJ
On 17 nov. 2015, at 08:10, Derk-Jan Hartman d.j.hartman+wmf_ml@gmail.com wrote:
Awesome !! And once more a thank you to Henrik who selflessly maintained his stats.grok.se for so many years !!!
DJ
On 17 nov. 2015, at 04:40, Rachel diCerbo rdicerb@wikimedia.org wrote:
This is fantastic news - thank you so much, Analytics, Services, Ops, and the communities who supported/requested this!
On Mon, Nov 16, 2015 at 1:50 PM, Dan Andreescu dandreescu@wikimedia.org wrote:
Dear Data Enthusiasts,
In collaboration with the Services team, the analytics team wishes to announce a public Pageview API https://wikimedia.org/api/rest_v1/?doc#!/Pageviews_data/get_metrics_pageviews_per_article_project_access_agent_article_granularity_start_end. For an example of what kind of UIs someone could build with it, check out this excellent demo http://analytics.wmflabs.org/demo/pageview-api (code) https://gist.github.com/marcelrf/49738d14116fd547fe6d#file-article-comparison-html .
The API can tell you how many times a wiki article or project is viewed over a certain period. You can break that down by views from web crawlers or humans, and by desktop, mobile site, or mobile app. And you can find the 1000 most viewed articles https://wikimedia.org/api/rest_v1/metrics/pageviews/top/es.wikipedia/all-access/2015/11/11 on any project, on any given day or month that we have data for. We currently have data back through October and we will be able to go back to May 2015 when the loading jobs are all done. For more information, take a look at the user docs https://wikitech.wikimedia.org/wiki/Analytics/AQS/Pageview_API.
After many requests from the community, we were really happy to finally make this our top priority and get it done. Huge thanks to Gabriel, Marko, Petr, and Eric from Services, Alexandros and all of Ops really, Henrik for maintaining stats.grok, and, of course, the many community members who have been so patient with us all this time.
The Research team’s Article Recommender tool http://recommend.wmflabs.org/ already uses the API to rank pages and determine relative importance. Wiki Education Foundation’s dashboard https://dashboard.wikiedu.org/ is going to be using it to count how many times an article has been viewed since a student edited it. And there are other grand plans for this data like “article finder”, which will find low-rated articles with a lot of pageviews; this can be used by editors looking for high-impact work. Join the fun, we’re happy to help get you started and listen to your ideas. Also, if you find bugs or want to suggest improvements, please create a task in Phabricator and tag it with #Analytics-Backlog https://phabricator.wikimedia.org/tag/analytics-backlog/.
So what’s next? We can think of too many directions to go into, for pageview data and Wikimedia project data, in general. We need to work with you to make a great plan for the next few quarters. Please chime in here https://phabricator.wikimedia.org/T112956 with your needs.
Team Analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
--
Rachel diCerbo Director of Community Engagement (Product) Wikimedia Foundation Rdicerb (WMF) https://meta.wikimedia.org/wiki/User_talk:Rdicerb_%28WMF%29 @a_rachel https://twitter.com/a_rachel _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
It's nice to finally this go live. Great work guys!!
On Mon, Nov 16, 2015 at 11:50 PM, Dan Andreescu dandreescu@wikimedia.org wrote:
Dear Data Enthusiasts,
In collaboration with the Services team, the analytics team wishes to announce a public Pageview API. For an example of what kind of UIs someone could build with it, check out this excellent demo (code).
The API can tell you how many times a wiki article or project is viewed over a certain period. You can break that down by views from web crawlers or humans, and by desktop, mobile site, or mobile app. And you can find the 1000 most viewed articles on any project, on any given day or month that we have data for. We currently have data back through October and we will be able to go back to May 2015 when the loading jobs are all done. For more information, take a look at the user docs.
After many requests from the community, we were really happy to finally make this our top priority and get it done. Huge thanks to Gabriel, Marko, Petr, and Eric from Services, Alexandros and all of Ops really, Henrik for maintaining stats.grok, and, of course, the many community members who have been so patient with us all this time.
The Research team’s Article Recommender tool already uses the API to rank pages and determine relative importance. Wiki Education Foundation’s dashboard is going to be using it to count how many times an article has been viewed since a student edited it. And there are other grand plans for this data like “article finder”, which will find low-rated articles with a lot of pageviews; this can be used by editors looking for high-impact work. Join the fun, we’re happy to help get you started and listen to your ideas. Also, if you find bugs or want to suggest improvements, please create a task in Phabricator and tag it with #Analytics-Backlog.
So what’s next? We can think of too many directions to go into, for pageview data and Wikimedia project data, in general. We need to work with you to make a great plan for the next few quarters. Please chime in here with your needs.
Team Analytics
Engineering mailing list Engineering@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering
This is awesome. Congratulations!
On Tue, Nov 17, 2015 at 9:28 AM, Alexandros Kosiaris < akosiaris@wikimedia.org> wrote:
It's nice to finally this go live. Great work guys!!
On Mon, Nov 16, 2015 at 11:50 PM, Dan Andreescu dandreescu@wikimedia.org wrote:
Dear Data Enthusiasts,
In collaboration with the Services team, the analytics team wishes to announce a public Pageview API. For an example of what kind of UIs
someone
could build with it, check out this excellent demo (code).
The API can tell you how many times a wiki article or project is viewed
over
a certain period. You can break that down by views from web crawlers or humans, and by desktop, mobile site, or mobile app. And you can find the 1000 most viewed articles on any project, on any given day or month that
we
have data for. We currently have data back through October and we will
be
able to go back to May 2015 when the loading jobs are all done. For more information, take a look at the user docs.
After many requests from the community, we were really happy to finally
make
this our top priority and get it done. Huge thanks to Gabriel, Marko,
Petr,
and Eric from Services, Alexandros and all of Ops really, Henrik for maintaining stats.grok, and, of course, the many community members who
have
been so patient with us all this time.
The Research team’s Article Recommender tool already uses the API to rank pages and determine relative importance. Wiki Education Foundation’s dashboard is going to be using it to count how many times an article has been viewed since a student edited it. And there are other grand plans
for
this data like “article finder”, which will find low-rated articles with
a
lot of pageviews; this can be used by editors looking for high-impact
work.
Join the fun, we’re happy to help get you started and listen to your
ideas.
Also, if you find bugs or want to suggest improvements, please create a
task
in Phabricator and tag it with #Analytics-Backlog.
So what’s next? We can think of too many directions to go into, for pageview data and Wikimedia project data, in general. We need to work
with
you to make a great plan for the next few quarters. Please chime in here with your needs.
Team Analytics
Engineering mailing list Engineering@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering
-- Alexandros Kosiaris akosiaris@wikimedia.org
Engineering mailing list Engineering@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering
This is *awesome*. Excellent work Team Analytics!
On Mon, Nov 16, 2015 at 9:50 PM, Dan Andreescu dandreescu@wikimedia.org wrote:
Dear Data Enthusiasts,
In collaboration with the Services team, the analytics team wishes to announce a public Pageview API https://wikimedia.org/api/rest_v1/?doc#!/Pageviews_data/get_metrics_pageviews_per_article_project_access_agent_article_granularity_start_end. For an example of what kind of UIs someone could build with it, check out this excellent demo http://analytics.wmflabs.org/demo/pageview-api (code) https://gist.github.com/marcelrf/49738d14116fd547fe6d#file-article-comparison-html .
The API can tell you how many times a wiki article or project is viewed over a certain period. You can break that down by views from web crawlers or humans, and by desktop, mobile site, or mobile app. And you can find the 1000 most viewed articles https://wikimedia.org/api/rest_v1/metrics/pageviews/top/es.wikipedia/all-access/2015/11/11 on any project, on any given day or month that we have data for. We currently have data back through October and we will be able to go back to May 2015 when the loading jobs are all done. For more information, take a look at the user docs https://wikitech.wikimedia.org/wiki/Analytics/AQS/Pageview_API.
After many requests from the community, we were really happy to finally make this our top priority and get it done. Huge thanks to Gabriel, Marko, Petr, and Eric from Services, Alexandros and all of Ops really, Henrik for maintaining stats.grok, and, of course, the many community members who have been so patient with us all this time.
The Research team’s Article Recommender tool http://recommend.wmflabs.org/ already uses the API to rank pages and determine relative importance. Wiki Education Foundation’s dashboard https://dashboard.wikiedu.org/ is going to be using it to count how many times an article has been viewed since a student edited it. And there are other grand plans for this data like “article finder”, which will find low-rated articles with a lot of pageviews; this can be used by editors looking for high-impact work. Join the fun, we’re happy to help get you started and listen to your ideas. Also, if you find bugs or want to suggest improvements, please create a task in Phabricator and tag it with #Analytics-Backlog https://phabricator.wikimedia.org/tag/analytics-backlog/.
So what’s next? We can think of too many directions to go into, for pageview data and Wikimedia project data, in general. We need to work with you to make a great plan for the next few quarters. Please chime in here https://phabricator.wikimedia.org/T112956 with your needs.
Team Analytics
Engineering mailing list Engineering@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering
Congratulations from me as well, especially since I was probably the one screaming for it the loudest (or the longest, or both...)
I'll now go and have good long lok at which tools to adapt, which to rewrite, and which to invent!
On Mon, Nov 16, 2015 at 9:50 PM Dan Andreescu dandreescu@wikimedia.org wrote:
Dear Data Enthusiasts,
In collaboration with the Services team, the analytics team wishes to announce a public Pageview API https://wikimedia.org/api/rest_v1/?doc#!/Pageviews_data/get_metrics_pageviews_per_article_project_access_agent_article_granularity_start_end. For an example of what kind of UIs someone could build with it, check out this excellent demo http://analytics.wmflabs.org/demo/pageview-api (code) https://gist.github.com/marcelrf/49738d14116fd547fe6d#file-article-comparison-html .
The API can tell you how many times a wiki article or project is viewed over a certain period. You can break that down by views from web crawlers or humans, and by desktop, mobile site, or mobile app. And you can find the 1000 most viewed articles https://wikimedia.org/api/rest_v1/metrics/pageviews/top/es.wikipedia/all-access/2015/11/11 on any project, on any given day or month that we have data for. We currently have data back through October and we will be able to go back to May 2015 when the loading jobs are all done. For more information, take a look at the user docs https://wikitech.wikimedia.org/wiki/Analytics/AQS/Pageview_API.
After many requests from the community, we were really happy to finally make this our top priority and get it done. Huge thanks to Gabriel, Marko, Petr, and Eric from Services, Alexandros and all of Ops really, Henrik for maintaining stats.grok, and, of course, the many community members who have been so patient with us all this time.
The Research team’s Article Recommender tool http://recommend.wmflabs.org/ already uses the API to rank pages and determine relative importance. Wiki Education Foundation’s dashboard https://dashboard.wikiedu.org/ is going to be using it to count how many times an article has been viewed since a student edited it. And there are other grand plans for this data like “article finder”, which will find low-rated articles with a lot of pageviews; this can be used by editors looking for high-impact work. Join the fun, we’re happy to help get you started and listen to your ideas. Also, if you find bugs or want to suggest improvements, please create a task in Phabricator and tag it with #Analytics-Backlog https://phabricator.wikimedia.org/tag/analytics-backlog/.
So what’s next? We can think of too many directions to go into, for pageview data and Wikimedia project data, in general. We need to work with you to make a great plan for the next few quarters. Please chime in here https://phabricator.wikimedia.org/T112956 with your needs.
Team Analytics _______________________________________________ Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Dan Andreescu wrote:
The API can tell you how many times a wiki article or project is viewed over a certain period. You can break that down by views from web crawlers or humans, and by desktop, mobile site, or mobile app. And you can find the 1000 most viewed articles https://wikimedia.org/api/rest_v1/metrics/pageviews/top/es.wikipedia/all- access/2015/11/11 on any project, on any given day or month that we have data for. We currently have data back through October and we will be able to go back to May 2015 when the loading jobs are all done.
This looks very promising. Congratulations to all on getting this launched!
I hit a bug involving gzip compression and HTTP headers that was quickly fixed (https://phabricator.wikimedia.org/T118817). Now that I'm lightly poking at the API's data, the "Paul_Elio" article on the English Wikipedia allegedly received 4,832,338 views on 2015-11-16, according to https://phabricator.wikimedia.org/P2325. This anomaly and a few others make me a bit wary about the accuracy of this data. That said, a lot of the results look about right and are easily explained ("Charlie_Sheen" and "November_2015_Paris_attacks" are easy examples).
MZMcBride
Nice work on the API!
I wrote a basic consumer of this API at http://codepen.io/Krinkle/full/wKOMMN#wikimdia-pageviews
The only hurdle I found is that the 'articles' property is itself nested/double encoded JSON, instead of a plain object. This was somewhat unexpected and makes the API harder to use.
Code at http://codepen.io/Krinkle/pen/wKOMMN?editors=001.
(Supported in Chrome, Firefox, Safari and IE10+)
On Wed, Nov 18, 2015 at 3:09 AM, MZMcBride z@mzmcbride.com wrote:
Dan Andreescu wrote:
The API can tell you how many times a wiki article or project is viewed over a certain period. You can break that down by views from web crawlers or humans, and by desktop, mobile site, or mobile app. And you can find the 1000 most viewed articles <
https://wikimedia.org/api/rest_v1/metrics/pageviews/top/es.wikipedia/all-
access/2015/11/11> on any project, on any given day or month that we have data for. We currently have data back through October and we will be able to go back to May 2015 when the loading jobs are all done.
This looks very promising. Congratulations to all on getting this launched!
I hit a bug involving gzip compression and HTTP headers that was quickly fixed (https://phabricator.wikimedia.org/T118817). Now that I'm lightly poking at the API's data, the "Paul_Elio" article on the English Wikipedia allegedly received 4,832,338 views on 2015-11-16, according to https://phabricator.wikimedia.org/P2325. This anomaly and a few others make me a bit wary about the accuracy of this data. That said, a lot of the results look about right and are easily explained ("Charlie_Sheen" and "November_2015_Paris_attacks" are easy examples).
MZMcBride
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Krinkle wrote:
The only hurdle I found is that the 'articles' property is itself nested/double encoded JSON, instead of a plain object. This was somewhat unexpected and makes the API harder to use.
I filed https://phabricator.wikimedia.org/T118931 about this.
MZMcBride wrote:
Now that I'm lightly poking at the API's data, the "Paul_Elio" article on the English Wikipedia allegedly received 4,832,338 views on 2015-11-16, according to https://phabricator.wikimedia.org/P2325.
I decided that the numbers for this page are strange enough to warrant an investigatory task: https://phabricator.wikimedia.org/T118933.
MZMcBride
Nice work on the API!
I wrote a basic consumer of this API at http://codepen.io/Krinkle/full/wKOMMN#wikimdia-pageviews
Cool! Check out dv.wikipedia.org though, some of the RTL is messing with your (N views) parens.
The only hurdle I found is that the 'articles' property is itself
nested/double encoded JSON, instead of a plain object. This was somewhat unexpected and makes the API harder to use.
Right, for sure. The data had to be stuffed that way to save space in Cassandra. So we could parse it and reshape the response in RESTBase, and that seems like a good idea and probably wouldn't hurt performance too much. Do you think it's worth the breaking change to the format? I'll post on the bug that MZ filed.
Quick general reminder. Please tag tasks with "Analytics-Backlog" instead of "Analytics" for now. We need to clean that up, but we just haven't gotten around to it.
On Wed, Nov 18, 2015 at 9:05 AM, Dan Andreescu dandreescu@wikimedia.org wrote:
Nice work on the API!
I wrote a basic consumer of this API at http://codepen.io/Krinkle/full/wKOMMN#wikimdia-pageviews
Cool! Check out dv.wikipedia.org though, some of the RTL is messing with your (N views) parens.
The only hurdle I found is that the 'articles' property is itself
nested/double encoded JSON, instead of a plain object. This was somewhat unexpected and makes the API harder to use.
Right, for sure. The data had to be stuffed that way to save space in Cassandra. So we could parse it and reshape the response in RESTBase, and that seems like a good idea and probably wouldn't hurt performance too much. Do you think it's worth the breaking change to the format? I'll post on the bug that MZ filed.
wikitech-l@lists.wikimedia.org