It would be nice to have a graph/graphs of edits over time in MediaWiki's info action.
See also
It would be nice to have a graph/graphs of edits over time in MediaWiki's info action.
See also
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | Feature | None | T40450 Reimplement MediaWiki's info action (tracking) | ||
Declined | None | T43326 Incorporate analytics into MediaWiki's info action | |||
Open | None | T43329 Add edit history graph(s) to MediaWiki's info action | |||
Resolved | Jdforrester-WMF | T45666 Implement scaleable graphing capability in a MediaWiki extension for Wikimedia wikis (tracking) |
Zak Greant wrote a Greasemonkey script "MediaWiki history Sparklines" which we might want to integrate:
http://userscripts.org/scripts/show/79234
That would be a nice experiment, can most probably be implemented as a Gadget too.
(In reply to comment #1)
Zak Greant wrote a Greasemonkey script "MediaWiki history Sparklines" which we
might want to integrate:
Neat!
That would be a nice experiment, can most probably be implemented as a Gadget
too.
Hmm, maybe. The nice thing here is that we have all of the data already (edit timestamp, page title) and it's indexed. The not-so-nice thing here is that the edge cases are a bit rough. Some pages have over 600,000 revisions.
Zak's user script is hitting the API. For small pages, this is fine. For large pages, this is probably impractical. If this feature were implemented as an extension, it could do direct queries on the database to get the underlying data and/or use a cache store/database table for larger pages.
https://gerrit.wikimedia.org/r/31603
Just a draft. If anybody can come up with a better way to draw graphs other than a jQuery extension, please do. I figured a JavaScript dependency would be easier to manage than a PHP dependency.
Also, it should be noted this is a bit of a draft. There is some polishing that can be done to make the graph look better.
Wondering whether to move this to Extension requests too, as per dependency on bug 43666?
I think MediaWiki core would expose this data. Consumers might include the Graph extension. The question is then where the code that takes the data and turns into a graph that's usable at action=info would live. I'm not sure about that part.
In action=history we have year/month selectors now, so a logical starting point would be an (approximate) count of edits by year. Could even start as a table, if plotting is an issue; I don't remember if the gnuplot situation improved.
With T45666: Implement scaleable graphing capability in a MediaWiki extension for Wikimedia wikis (tracking) resolved, I don't think implementing this should be very difficult, at least for most pages.
This page looks helpful/useful: https://www.mediawiki.org/wiki/Extension:Graph/Demo/OverviewDetail.
@MZMcBride: I don't think this task is well-described with pointers to help the contributor and falls under good first task?
Currently the tags on this task imply that it's about writing a new extension from scratch (MediaWiki-extension-requests) but maybe that's not the case and this is just MediaWiki-General core territory now?
I don't think an extension is needed right now.
Writing a client-side JavaScript implementation should be fairly straightforward. The heavy lifts are building a graphing library and exposing the revision data in an API, both of which are now resolved.
A junior developer could dump data from an api.php call to a page similar to https://www.mediawiki.org/wiki/Extension:Graph/data/sp500-csv and then build a graph simliar to https://www.mediawiki.org/wiki/Extension:Graph/Demo/OverviewDetail. That would be a start.
From what I remember about Zak Greant "MediaWiki history Sparklines" script, I would say that the Revision-Slider extension is an appropriate response to this task.
It is available as a beta feature and is going to be enabled by default on mediawiki.org right now ( https://gerrit.wikimedia.org/r/319540 T149724 ).