we plan to drop the wb_entity_per_page table sometime soon, because
it is just not required (as we will likely always have a programmatic
mapping from entity id to page title) and it does not supported non
-numeric entity ids as it is now. Due to this removing it is a blocker
for the commons metadata.
Is anybody using that for their tools (on tool labs)? If so, please
tell us so that we can give you instructions and a longer grace period
to update your scripts.
Jura1 created a wonderful list of people who died in Brazil in 2015 . It
is a page that may update regularly from Wikidata thanks to the
ListeriaBot. Obviously, there may be a few more because I am falling ever
more behind with my quest for registering deaths in 2015.
I have copied his work and created a page for people who died in the
Netherlands in 2015 . It is trivially easy to do this and, the result is
great. The result looks great, it can be used for any country in any
The Dutch Wikipedia indicated that they nowadays maintain important
metadata at Wikidata. I am really happy that we can showcase their work. It
is important work because as someone reminded me at some stage, this is
part of what amounts to the policy of living people...
Lydia (or somebody operating the @Wikidata handle :) posted this question
on Twitter and a few great ideas started trickling in
I went ahead and created an AllOurIdeas poll <https://t.co/IbsBmY6Kpg>,
seeded with the first ideas posted on Twitter, to crowdsource the
generation of new ideas and produce a robust ranking.
If you're unfamiliar with AllOurIdeas </>, it's an open consultation engine
allowing people to choose which idea they like best via pairwise
comparisons (I am cc'ing Matt Salganik, the project lead). It's very simple
on the surface but it uses algorithms such as the Condorcet method
<https://en.wikipedia.org/wiki/Condorcet_method> to test how strongly each
idea performs against another, reducing the weighing of the oldest ideas to
create a level playing field for newly created ideas and preventing gaming
or self-promotion of one's own ideas.
Try it out or post new ideas: the more votes it gets, the higher the
confidence of the ranking. Real-time results and statistics are here
looking into  I read that Wikidata supports 358 languages. Is it still
true? For example, I tried to add label in language coded as "nan" (defined
in ISO 639-3) and it worked. However it didn't worked for e.g. "arb", which
is also part of the ISO 639-3 standard. So how many?
 VRANDEČIĆ, Denny, KRÖTZSCH, Markus. Wikidata: A Free Collaborative
Knowledgebase. *Communications of the ACM*. 2014-10, Vol. 57 No. 10, 7885.
DOI 10.1145/2629489. http://cacm.acm.org/magazines/2014/10/178785-wikidata
Hey folks :)
Charlie has been working on concepts for making it possible to edit
Wikidata from Wikipedia and other wikis. This was her bachelor thesis. She
has now published it:
I am very happy she put a lot of thought and work into figuring out all the
complexities of the topic and how to make this understandable for editors.
We still have more work to do on the concepts and then actually have to
implement it. Comments welcome.
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
Currently, the primary sources tool maintenance and improvement
processes are fairly sub-optimal, as:
1. the core team at Google has not enough time to tackle bugs and
2. the pull request/merge flow is insufficient alone, since both the
back-end and the front-end must also be deployed in production,
eventually by someone else.
I would like to report here the requirements to make the tool sustainable:
A. a developer to understand the back-end code , written in C++;
C. access to the WMF Labs machine to deploy the back-end ;
D. a Wikidata administrator to deploy the front-end ;
E. centralized and exhaustive documentation.
As part of the StrepHit project goals , my team is striving to help
with A. (not exactly trivial) and C., but we really need B. and D. to be
On 5/31/16 14:00, wikidata-request(a)lists.wikimedia.org wrote:
> Date: Tue, 31 May 2016 08:47:18 +0000 From: Sebastian Schaffert
> <schaffert(a)google.com> To: Thomas Steiner <tomac(a)google.com>,
> "Discussion list for the Wikidata project."
> <wikidata(a)lists.wikimedia.org> Subject: Re: [Wikidata] Primary sources
> tool "reject claim" broken? Message-ID:
> Content-Type: text/plain; charset="utf-8" Hi Thomas and all, there might
> be a caching issue here. That part of the code is here:
> and it still seems right to me, but I'll check again. I won't have much
> time in the next days though :( I'll give it one hour no, maybe I
> discover something. Cheers, Sebastian On Tue, May 31, 2016 at 9:17 AM
> Thomas Steiner <tomac(a)google.com> wrote:
>> >Hi Markus and Marco, all,
>> >Thanks for your support of and caring for the Primary Sources Tool.
>> >Please find my replies inline.
>>> > >Dear <whoever is maintaining the PS gadget now>,
>> >I guess the core team still does, with the caveat explained by Denny
>> >in , the tl;dr is that we work on it on top of our regular jobs and
>> >that we are happy to hand it over to folks with more time on their
>>> > >The PS tool seems to break more and more. Besides the persisting issue
>>> > >duplicated claims being offered (even if they are already stored), there
>>> > >now also the issue that claims cannot be rejected. If I reject a claim,
>>> > >page reloads, but the suggestion still shows up after that.
>> >I checked both problems. It seems the writes from the front-end
>> >somehow do not make it to the back-end. I opened a random item Q632229
>> >and approved and rejected claims. The approval went through just fine
>> >(i) However, I could reproduce the duplicate claims being shown, the
>> >reason is that the uniqueness comparison does not take references into
>> >account , a known @ToDo up for grabs.
>> >(ii) I could also in some cases reproduce the non-rejectable claims
>> >issue. I repeated disapproved statement 868483 , but if you query
>> >the back-end for incoming Freebase statements for Q632229, it keeps
>> >coming back as "unapproved"  (search for "868483").
>> >For (i), if someone wants to tackle this, happy to merge their Pull
>> >Request. For (ii), Sebastian, do you have a suspicion why this could
>> >be the case?
>> >Dr. Thomas Steiner, Employee (http://blog.tomayac.com,
>> >Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany
>> >Managing Directors: Matthew Scott Sucherman, Paul Terence Manicle
>> >Registration office and registration number: Hamburg, HRB 86891
>> >-----BEGIN PGP SIGNATURE-----
>> >Version: GnuPG v2.0.29 (GNU/Linux)
>> >-----END PGP SIGNATURE-----
Dear <whoever is maintaining the PS gadget now>,
The PS tool seems to break more and more. Besides the persisting issue
with duplicated claims being offered (even if they are already stored),
there is now also the issue that claims cannot be rejected. If I reject
a claim, the page reloads, but the suggestion still shows up after that.
Faculty of Computer Science
Technische Universität Dresden
+49 351 463 38486
this is a known issue:
It seems to be related to the front-end: @Thomas, this and
https://github.com/google/primarysources/issues/107 are blocking the
usage of the tool.
Would it be possible for you to investigate them?
On 5/30/16 14:00, wikidata-request(a)lists.wikimedia.org wrote:
> Date: Mon, 30 May 2016 10:19:32 +0200
> From: Markus Kroetzsch<markus.kroetzsch(a)tu-dresden.de>
> To: "Discussion list for the Wikidata project."
> Subject: [Wikidata] Primary sources tool "reject claim" broken?
> Content-Type: text/plain; charset=utf-8; format=flowed
> Dear <whoever is maintaining the PS gadget now>,
> The PS tool seems to break more and more. Besides the persisting issue
> with duplicated claims being offered (even if they are already stored),
> there is now also the issue that claims cannot be rejected. If I reject
> a claim, the page reloads, but the suggestion still shows up after that.
> -- Markus Kroetzsch Faculty of Computer Science Technische Universität
> Dresden +49 351 463 38486 http://korrekt.org/