Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
When a page is moved, the pageview tool doesn't report views of the page at the old location #26
Take as an example the English Wikipedia article on "First observation of gravitational waves". At present, the page view statistics link on the 'view history' page points to:
Ideally, the tool would report the page view statistics for the page at both its current location and any previous locations. Would this be possible, please?
Yes, this particular scenario can be resolved with #9, which I hope to implement soon. In most cases it won't be a big deal, but there are performance issues I'll need to sort out for articles with lots of redirects, like Google. For this reason including redirects as a single statistic will be optional, defaulted-off.
This still isn't fool-proof for page moves, as one could move the page, then a new article created at the old location. There is #16 where we'd allow entering a page ID, which stays intact with page moves, however the Pageviews API goes by page name – so we end up with the same issue.
The only real solution is to recursively check a given page's move log, collect page view data on each such that we end up with accurate data for the full date range. This is not easy to do... and could be very expensive in terms of performance.
@kaldari You don't think checking the move log would be worthwhile? That's one API call, followed by N more for each entry in the move log that falls within our date range. It shouldn't be too expensive, and I think will offer more accurate representation of what the user probably wants than including data on the redirects. For instance, an old location may have become a different article entirely, and never became a redirect to the new location.
Of course, it is still a lot of work! I say let's wait for T121912 to be resolved and go from there.