For all Hive users using stat1002/1004, you might have seen a deprecation
warning when you launch the hive client - that claims it's being replaced
with Beeline. The Beeline shell has always been available to use, but it
required supplying a database connection string every time, which was
pretty annoying. We now have a wrapper
setup to make this easier. The old Hive CLI will continue to exist, but we
encourage moving over to Beeline. You can use it by logging into the
stat1002/1004 boxes as usual, and launching `beeline`.
There is some documentation on this here:
If you run into any issues using this interface, please ping us on the
Analytics list or #wikimedia-analytics or file a bug on Phabricator
(If you are wondering stat1004 whaaat - there should be an announcement
coming up about it soon!)
Forwarding this question to the public Analytics list, where it's good to
have these kinds of discussions. If you're interested in this data and how
it changes over time, do subscribe and watch for updates, notices of
Ok, so on to your question. You'd like the *total # of articles for each
wiki*. I think the simplest way right now is to query the AQS (Analytics
Query Service) API, documented here:
To get the # of articles for a wiki, let's say en.wikipedia.org, you can
get the timeseries of new articles per month since the beginning of time:
And to get a list of all wikis, to plug into that URL instead of "
en.wikipedia.org", the most up-to-date information is here:
https://meta.wikimedia.org/wiki/Special:SiteMatrix in table form or via the
Sometimes new sites won't have data in the AQS API for a month or two until
we add them and start crunching their stats.
The way I figured this out is to look at how our UI uses the API:
So if you were interested in something else, you can browse around there
and take a look at the XHR requests in the browser console. Have fun!
On Thu, Mar 29, 2018 at 12:54 AM, Zainan Zhou (a.k.a Victor) <zzn(a)google.com
> Hi Dan,
> How are you! This is Victor, It's been a while since we meet at the 2018
> Wikimedia Dev Summit. I hope you are doing great.
> As I mentioned to you, my team works on extracting the knowledge from
> Wikipedia. Currently it's undergoing a project that expands language
> coverage. My teammate Yuan Gao(cc'ed here) is tech leader of this
> project.She plans to *monitor the list of all the current available
> wikipedia's sites and the number of articles for each language*, so that
> we can compare with our extraction system's output to sanity-check if there
> is a massive breakage of the extraction logic, or if we need to add/remove
> languages in the event that a new wikipedia site is introduced to/remove
> from the wikipedia family.
> I think your team at Analytics at Wikimedia probably knows the best where
> we can find this data. Here are 4 places we already know, but doesn't seem
> to have the data.
> - https://en.wikipedia.org/wiki/List_of_Wikipedias. has the
> information we need, but the list is manually edited, not automatic
> - https://stats.wikimedia.org/EN/Sitemap.htm, has the full list, but
> the information seems pretty out of date(last updated almost a month ago)
> - StatsV2 UI: https://stats.wikimedia.org/v2/#/all-projects, I can't
> find the full list nor the number of articles
> - API https://wikimedia.org/api/rest_v1/ suggested by elukey on
> #wikimedia-analytics channel, it doesn't seem to have # of article
> Do you know what is a good place to find this information? Thank you!
> * • **Zainan Zhou(**周载南**) a.k.a. "Victor" * <http://who/zzn>
> * • *Software Engineer, Data Engine
> * •* Google Inc.
> * • *zzn(a)google.com <ecarmeli(a)google.com> - 650.336.5691
> * • * 1600 Amphitheathre Pkwy, LDAP zzn, Mountain View 94043
> ---------- Forwarded message ----------
> From: Yuan Gao <gaoyuan(a)google.com>
> Date: Wed, Mar 28, 2018 at 4:15 PM
> Subject: Monitor the number of Wikipedia sites and the number of articles
> in each site
> To: Zainan Victor Zhou <zzn(a)google.com>
> Cc: Wenjie Song <wenjies(a)google.com>, WikiData <wikidata(a)google.com>
> Hi Victor,
> as we discussed in the meeting, I'd like to monitor:
> 1) the number of Wikipedia sites
> 2) the number of articles in each site
> Can you help us to contact with WMF to get a realtime or at least daily
> update of these numbers? What we can find now is
> https://en.wikipedia.org/wiki/List_of_Wikipedias, but the number of
> Wikipedia sites is manually updated, and possibly out-of-date.
> The monitor can help us catch such bugs.
> Yuan Gao
there is an ongoing task for Eventlogging (
https://phabricator.wikimedia.org/T200630) related to the parsing of weird
user agents. The issue caused Eventlogging to be down during the weekend,
but we hope to make it work again today. This implies that recent data is
delayed, apologies for the inconvenience.
For any question feel free to reach out to the Analytics team via the usual
channels (IRC #wikimedia-analytics, emails, etc..).
Forwarding in case this is of interest to anyone on the Analytics or
Research lists who doesn't subscribe to Wikitech-l or Xmldatadumps-l.
( https://meta.wikimedia.org/wiki/User:Pine )
---------- Forwarded message ----------
From: Ariel Glenn WMF <ariel(a)wikimedia.org>
Date: Fri, Jul 20, 2018 at 5:53 AM
Subject: [Wikitech-l] hewiki dump to be added to 'big wikis' and run with
To: Wikipedia Xmldatadumps-l <Xmldatadumps-l(a)lists.wikimedia.org>,
Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
The pages-meta-history dumps for hewiki take 70 hours these days, the
longest of any wiki not already running with parallel jobs. I plan to add
it to the list of 'big wikis' starting August 1st, meaning that 6 jobs will
run in parallel producing the usual numbered file output; look at e.g.
frwiki dumps for an example.
Please adjust any download/processing scripts accordingly.
Wikitech-l mailing list
[Adding some other mailing lists in Cc]
as a lot of you have probably already noticed yesterday reading the
operations@ mailing list, we had an outage of the Kafka Main eqiad cluster
that forced us to switch the Eventbus and Eventstreams services to codfw.
All the precise timings will be listed in
but for a quick glimpse:
2018-07-11 17:00 UTC - Eventbus service switched to codfw
2018-07-11 18:44 UTC - Eventstreams service switched to codfw
We are going to switch back those services to eqiad during the next couple
of hours. The consumers of the Eventstreams service may get some failures
or data drops, apologies in advance for the trouble.
Il giorno gio 12 lug 2018 alle ore 00:00 Luca Toscano <
ltoscano(a)wikimedia.org> ha scritto:
> Hi everybody,
> as you might have seen from the operations' channel on IRC the Kafka Main
> Eqiad cluster (kafka100[1-3].eqiad.wmnet) suffered a long outage due to new
> topics pushed out with too long names (causing fs operation issues, etc..).
> I'll update this email thread tomorrow EU time with more details, tasks,
> precise root cause, etc.., but the important bit to know is that Eventbus
> and Eventstreams have been failed over to the Kafka Main Codfw cluster.
> This should be transparent to everybody but please let us know otherwise.
> Thanks for the patience!
> (a very sleepy :) Luca
The next Wikimedia Research Showcase will be live-streamed Wednesday, July
11, 2018 at 11:30 AM (PDT) 18:30 UTC.
YouTube stream: https://www.youtube.com/watch?v=uK7AvNKq0sg
As usual, you can join the conversation on IRC at #wikimedia-research. And,
you can watch our past research showcases here.
Hope to see you there!
This month's presentations:
Mind the (Language) Gap: Neural Generation of Multilingual Wikipedia
Summaries from Wikidata for ArticlePlaceholdersBy *Lucie-Aimée Kaffee*While
Wikipedia exists in 287 languages, its content is unevenly distributed
among them. It is therefore of the utmost social and cultural interests to
address languages for which native speakers have only access to an
impoverished Wikipedia. In this work, we investigate the generation of
summaries for Wikipedia articles in underserved languages, given structured
data as an input.
In order to address the information bias towards widely spoken languages,
we focus on an important support for such summaries: ArticlePlaceholders,
which are dynamically generated content pages in underserved Wikipedia
versions. They enable native speakers to access existing information in
Wikidata, a structured Knowledge Base (KB). Our system provides a
generative neural network architecture, which processes the triples of the
KB as they are dynamically provided by the ArticlePlaceholder, and generate
a comprehensible textual summary. This data-driven approach is tested with
the goal of understanding how well it matches the communities' needs on two
underserved languages on the Web: Arabic, a language with a big community
with disproportionate access to knowledge online, and Esperanto.
With the help of the Arabic and Esperanto Wikipedians, we conduct an
extended evaluation which exhibits not only the quality of the generated
text but also the applicability of our end-system to any underserved
Wikipedia version. Token-level change tracking: data, tools and
Flöck*This talk first gives an overview of the WikiWho infrastructure,
which provides tracking of changes to single tokens (~words) in articles of
different Wikipedia language versions. It exposes APIs for accessing this
data in near-real time, and is complemented by a published static dataset.
Several insights are presented regarding provenance, partial reverts,
token-level conflict and other metrics that only become available with such
data. Lastly, the talk will cover several tools and scripts that are
already using the API and will discuss their application scenarios, such as
investigation of authorship, conflicted content and editor productivity.
We are experiencing problems with this tool:
https://tools.wmflabs.org/commons-video-clicks/help.html#, the tool for
measuring the number of plays is not functioning at present.
Can you please suggest alternative tools to see the number of plays for
these 14 x OER MOOC video snippets attached we have uploaded to Wikimedia
Commons and inserted into relevant Wikipedia pages?
Thank you very much!
*Agnes Bruszik - *Programme Evaluation Assistant
*Wikimedia UK* is the national chapter for the global Wikimedia open
knowledge movement. We rely on donations from individuals to support our
work to make knowledge open for all. Have you considered supporting
Wikimedia UK is a Company Limited by Guarantee registered in England and
Wales, Registered No. 6741827. Registered Charity No.1144513. Registered
Office 4th Floor, Development House, 56-64 Leonard Street, London EC2A 4LT.
United Kingdom. Wikimedia UK is the UK chapter of a global Wikimedia
movement. The Wikimedia projects are run by the Wikimedia Foundation (who
operate Wikipedia, amongst other projects).
*Wikimedia UK is an independent non-profit charity with no legal control
over Wikipedia nor responsibility for its contents.*
I'm happy to announce the launch of the Inspire Campaign on Measuring
Community Health. The goal of this campaign is to gather your ideas on
approaches to measure or evaluate the experience and quality of
participating and interacting with others in Wikimedia projects.
So what is community health? Healthy projects promote high quality content
creation, respectful collaboration, efficient workflows, and effective
conflict resolution. Tasks and experiences that result in patterns of
editor frustration, poor editor retention, harassment, broken workflows,
and unresolved conflicts are unhealthy for a project.
As a movement, Wikimedians have always measured aspects of their
communities. Data points, such as editor activity levels, are regularly
collected. While these metrics provide some useful indications about the
health of a project, they do not give major insights into challenges and
specific areas needing improvement or what areas have been successful.
We want to hear from you what specific areas on your Wikimedia project
should be evaluated or measured, and how it should be done. Share your
ideas, contribute to other people’s submissions, and get involved in the
new Inspire Campaign. After the campaign, grants and other paths are
available to support the formal development of these measures and
Trust and Safety Specialist
Trust and Safety team;
Anti-harassment tools team