A problem with the category hierarchy is that any rather out of place subcategory brings in a full branch of anomalous subjects below it.
Thus making a report like https://stats.wikimedia.org/wikimedia/pageviews/categorized/wp-en/2015-06/pageviews_wp-en_cat_WikiProject_Medicine_2015-06.html involved cyclic pruning of weird subbranches, manually building a blacklist of nodes not to follow, that I could feed into the script.
The other project, I gave up https://stats.wikimedia.org/EN/CategoryOverviewIndex.htm as it became too unwieldy. Also, sometimes a category re-appeared as a great-grandchild of itself. I had to detect that, in order to avoid loops.
Those are two of the pitfalls.
As for navigation: Even a smallish ('concise') example of how my second project https://stats.wikimedia.org/EN/CategoryOverview_EN_Concise.htm makes it daunting. What I often see is a dynamic navigator that shows one level up or down, which makes me feel I'm in a maze.
Erik
From: Analytics [mailto:analytics-bounces@lists.wikimedia.org] On Behalf Of Dan Andreescu
Sent: Monday, November 27, 2017 16:14
To: A mailing list for the Analytics Team at WMF and everybody who has an interest in Wikipedia and analytics. <analytics@lists.wikimedia.org>
Subject: Re: [Analytics] Tool to visualize which wiki pages link to which wiki pages?
Hi Andre. Jaime's query is a good starting point, it would get you the data you need for one wiki. We can import the templatelinks table and then we can run it on Hadoop and get all wikis at once (we already have the other tables).
But once we got that, we'd have a graph with millions of nodes and edges. That's not possible to consume in visual form, so you could serve slices of the data and visualize parts of the graph. The question is, then, what purpose would this visualization have? If that's well defined, maybe we can figure out what slices of the data would be most useful.
On Tue, Nov 21, 2017 at 2:04 PM, Joseph Allemandou <jallemandou@wikimedia.org> wrote: