#Notable people like any people die. The more notable they are, the more articles there are about them on the many Wikipedias.
Many issues resolve themselves when a person dies and consequently, death is a moment where Wikipedia articles are revisited.
When a recent death is registered on Wikidata, it makes sense to inform all the Wikipedias that have an article. The first thing that is needed is for Wikidata to be able to show these most recent deaths.
Thanks,
GerardM
Sunday, November 03, 2013
Arboga, a stad in #Sweden
Arboga is a municipality in Sweden. Like many others it once enjoyed town privileges, thus it is entitled to call itself stad. As you can imagine, there has been a constant change in the size and the relevance of these places. All the pertinent facts are maintained by the Swedish authorities and, it is possible to update the items of the Swedish municipalities in this way.
Much of the data about these municipalities has been harvested from the English language Wikipedia. Research on the quality of the data indicated that 96% of the data is correct. People from the Swedish community had hoped for 98% and, their aim is to raise the reliability of the information on Wikidata to 99,8%.
As they started their project, they found that the "communcode" or "towncode" was missing. This information is critical if automated updates from the Swedish authorities are to be considered. There are 2190 towns and communes and automated updates is what makes it feasible to realise the 99,8% reliability objective.
Setting this up is doable. The big question is who will maintain it once it has been set up. When you consider this problem for all countries and when you expand it to other domains, it becomes obvious that this needs serious consideration.
Thanks,
GerardM
Much of the data about these municipalities has been harvested from the English language Wikipedia. Research on the quality of the data indicated that 96% of the data is correct. People from the Swedish community had hoped for 98% and, their aim is to raise the reliability of the information on Wikidata to 99,8%.
As they started their project, they found that the "communcode" or "towncode" was missing. This information is critical if automated updates from the Swedish authorities are to be considered. There are 2190 towns and communes and automated updates is what makes it feasible to realise the 99,8% reliability objective.
Setting this up is doable. The big question is who will maintain it once it has been set up. When you consider this problem for all countries and when you expand it to other domains, it becomes obvious that this needs serious consideration.
Thanks,
GerardM
Friday, November 01, 2013
Looking for a better version to restore and make it generally available
This is the last Ottoman sultan and his grand vizier praying before they flee their country. They take their time to pray. Love it or hate it, this is a historic picture.
When you have a high resolution version of this picture, we want it badly. Your picture will be restored as much as possible. Sadly, this picture has too low a resolution.
Thanks,
GerardM
Thursday, October 31, 2013
#divcon - the first update about #Wikidata queries
The WikiDataQuery has a back-end that is a bit more sophisticated. Every 10 minutes or so the data used for the queries is updated.
Thanks,
GerardM
- The number of males in Wikidata is currently 798,999
- The number of females in Wikidata is currently 152,157
- There are 392,794 persons without their sex identified
Thanks,
GerardM
#divcon - The current number of #males and #females in #Wikidata
With the WikiDataQuery it is easy to learn the number of males (798,920) and females (152,118) known in Wikidata. It is based on the last dump. Real time query is being worked on.
These are de-duplicated numbers of males and females that have none or more Wikipedia articles.
Thanks,
GerardM
Ron Woodroof, an #American activist
This weekend I will speak at the #Wikimedia #diversity conference in Berlin. The conference aims to increase the pool of knowledge in the Wikimedia projects and to enable a heterogeneous, colourful, diverse community.
There will be a focus on the imbalance in the gender participation in our projects. There is also an imbalance in how subjects are covered
Ron Woodroof was an activist who is getting more attention these days because the movie "Dallas Buyers Club" is centred around him. He is notable enough for the Swedish to have an article written in 2012 about him. In the English version he was nothing but a redirect to the movie.
Love him or hate him. Mr Woodroof is notable. He is part of an anti-culture in the USA, he died of AIDS. It will be interesting to notice how many similar stories will be told at the conference.
Thanks,
GerardM
There will be a focus on the imbalance in the gender participation in our projects. There is also an imbalance in how subjects are covered
Ron Woodroof was an activist who is getting more attention these days because the movie "Dallas Buyers Club" is centred around him. He is notable enough for the Swedish to have an article written in 2012 about him. In the English version he was nothing but a redirect to the movie.
Love him or hate him. Mr Woodroof is notable. He is part of an anti-culture in the USA, he died of AIDS. It will be interesting to notice how many similar stories will be told at the conference.
Thanks,
GerardM
#Gapminder, the #Ignorance project
When the aim is to share in the sum of all knowledge, it seems obvious that ignorance is the ultimate enemy that is to be defeated. To defeat ignorance you have to get the facts straight.
Gapminder and Hans Rosling are well known for bringing an insight based on published facts, statistics and visualisation. The presentations are world class and the next insight they are seeking is the ignorance people have about our world.
It is not to gloat but to bring home the message that we do not know basic information about our world. With such an attitude you want to do better and bringing attention to ignorance implies that you want to ensure that people are better informed. Informing or sharing the sum of all knowledge is what the Wikimedia Foundation does best in its projects.
By covering 280+ languages most people who can read and have access to the Internet can be reached. It is "just" a matter of making this information available to all of them on a platform they use. Wikipedia is that platform and Wikidata is where the data should get a home.
There are two issues stopping us for now. Wikidata does not yet support the property type "value" and, we do not have the visualisation tools yet. Both can be helped, support for the property value is in the pipe line. Seeking cooperation with Gapminder seems an obvious thing to do.
Thanks,
GerardM
Gapminder and Hans Rosling are well known for bringing an insight based on published facts, statistics and visualisation. The presentations are world class and the next insight they are seeking is the ignorance people have about our world.
It is not to gloat but to bring home the message that we do not know basic information about our world. With such an attitude you want to do better and bringing attention to ignorance implies that you want to ensure that people are better informed. Informing or sharing the sum of all knowledge is what the Wikimedia Foundation does best in its projects.
By covering 280+ languages most people who can read and have access to the Internet can be reached. It is "just" a matter of making this information available to all of them on a platform they use. Wikipedia is that platform and Wikidata is where the data should get a home.
There are two issues stopping us for now. Wikidata does not yet support the property type "value" and, we do not have the visualisation tools yet. Both can be helped, support for the property value is in the pipe line. Seeking cooperation with Gapminder seems an obvious thing to do.
Thanks,
GerardM
Remove erroneous #constraints from #Wikidata
When a particular property is used, like the P218, that is ISO 639-1 to you, you can expect specific values to be associated with them. There is a list of constraints expected on the talk page. For the constraints mentioned, a list with constraint violations is published.
The point of such a list is to find members of the Wikidata community to cooperate and fix those errors.
One constraint used on many properties is associated with the deprecated property P107, the "main type (GND)". Many a list of constraint violations are regularly generated like this one for the P218.
When asked, it was NOT thought to be a good idea to remove all the erroneous constraint reports that are based on a false premise. So far I have constrained myself from uttering profanities. It is better to make the case and make the case publicly and loudly.
Thanks,
GerardM
The point of such a list is to find members of the Wikidata community to cooperate and fix those errors.
One constraint used on many properties is associated with the deprecated property P107, the "main type (GND)". Many a list of constraint violations are regularly generated like this one for the P218.
When asked, it was NOT thought to be a good idea to remove all the erroneous constraint reports that are based on a false premise. So far I have constrained myself from uttering profanities. It is better to make the case and make the case publicly and loudly.
Thanks,
GerardM
Wednesday, October 30, 2013
Missing labels in #Wikidata; a call for #data driven #user #participation
As more Wikidata items gain statements, people may benefit from the new information provided. That is, when there is a label for the properties and related items. When there is no label you will see a property or item identifier.
It is extremely annoying and, it is why I use Wikidata in English and not in Dutch.
When every reference to a missing label is registered for a period of 30 days, it becomes easy to suggest to our community what needs to be done to improve the usefulness of the data provided. As more of the high impact labels are translated, users will get more pertinent information.
The beauty of this suggestion is that it involves only the Wikidata development team. This makes it easy to implement. All these new labels will enlarge the number of items to search from.
An experiment like this, is like putting a toe in the water; data is accumulated to point to where our community involvement does the most good. Once there is some clarity that data driven user participation makes an impact, there are many more opportunities to explore..
Let us start with this easy opportunity.
Thanks,
GerardM
It is extremely annoying and, it is why I use Wikidata in English and not in Dutch.
When every reference to a missing label is registered for a period of 30 days, it becomes easy to suggest to our community what needs to be done to improve the usefulness of the data provided. As more of the high impact labels are translated, users will get more pertinent information.
The beauty of this suggestion is that it involves only the Wikidata development team. This makes it easy to implement. All these new labels will enlarge the number of items to search from.
An experiment like this, is like putting a toe in the water; data is accumulated to point to where our community involvement does the most good. Once there is some clarity that data driven user participation makes an impact, there are many more opportunities to explore..
Let us start with this easy opportunity.
Thanks,
GerardM
Magnus, master of #Wikimedia #tools
When Magnus agreed to answer some questions, I wanted his answers to have impact. So I asked a few influential people what they would ask Magnus. I am happy both with the questions and the answers; they offer us plenty opportunities for making more of an impact.
Thanks,
GerardM
Lydia: what's his next cool hack
Thanks,
GerardM
Lydia: what's his next cool hack
Technically, since the moment I received these questions, it would be AutoLists.
I haven't decided what to do after this. There is the prospect of extending/rewriting the Free Image Search Tool to use Wikidata, and to suggest images for Wikidata from the various Wikimedia projects in return.
Also, with the long-term plans to use Wikidata, or at least its software, to finally get a grip on metadata for files on Commons, it might be interesting to create and seed a database for the "obvious cases", which could then in turn seed "Wikidata Commons", when it finally shows up.Lydia: and what he'd like to do but doesn't get to (so others can do it)
A million things! Many of my tools could do with some fixing, code review, extension, you name it. If you can code, have a look at the existing tools and maybe sign up for a tool or two which you would like to improve (not just mine, of course!).
I still have to port tools from the toolserver. Have a look here at tools to port and, help me prioritise!
Another thing I had started back on the toolserver was a "tool pipeline", where you could chain up tools so that the output of one tool is the input of the next. This could be quite powerful, especially for less tech-savy users who can't write their own glue code, even if the concept sounds uncomfortably like the human centipede ;-) Have a look at my attempt back in 2012.Brion: What's the awesomest tool you've created that people don't (yet?) know about?
That's a hard one, as I carefully and thoroughly spam the community for every new tool I create ;-)
One that is probably less known, and that I use myself on Wikipedia, is a special CSS for wide screens, where it shows the Wikipedia main text in a central column, and arranges TOC, infoboxes, thumbnails, and small tables on the left or right. Screenshot & CSS
As for actual running code, less known but with huge potential IMHO, are live category intersects on Wikipedia. Together with [[User:Obiwankenobi]], we came up With this: Screenshot JSBrion: What's the best way to make things happen? (getting cool projects done, even if nobody else is working on them yet
Have something to show people. Even if it's little more than a mock-up. Even if it's full of bugs, slow, ugly, fails half the time, and does only 1% of what it should do. A single thing that people can see and click on can get people to the cause, where a hundred pages of text will not. Stallman's GNUpedia existed on a mailing list with many a fancy idea; Wikipedia was there to see, to "touch", to edit. Even if it was a single, bare Perl script.Alolita: what are your recommendations are for the next 5 innovative tools WMF needs to fund to build for Wikimedia websites
Not sure about funding for tools; coding projects big enough to fund should probably be designed as Wiki(m|p)edia-default extensions, or even MediaWiki core. In terms of new functionality prioritised in-house beyond the current scope, these would be the most interesting ones for me:
Alolita: How WMF can help support the development community better * process recommendations * policy recommendations * participation in helping grow more developer contributors
- OSM integration. This has been on the WMF back burner for years.
- Commons file metadata as Wikidata. On Wikidata itself, or added to Commons itself.
- More data for Tools Labs. View data so that we can support GLAM projects; there has been some talk about this lately, but it has been a few weeks away for years now. Also, faster access to the wikitext than through the API/dumps would be useful.
- Add Wikispecies to Wikidata. It might revive Wikispecies (which seems sadly underused), or at least rescue much of its information onto Wikidata.
- One old pet idea of mine: Wikimedia (bi-)weekly magazine. Consider an amalgamate of Wikinews (which, let's face it, has pretty much failed as a daily source of news), Wikipedia "did you know"-type interesting articles, interesting places from Wikivoyage (which appears to be booming), fascinating images from Commons, an excerpt from Wikibooks, a short story from Wikisource, you get the idea. An editorial text, or political comment (relevant to the Wikimedia world; think CISPA), from individuals might not be too far fetched an idea. An issue would be generated in the usual fashion, maybe with an editor-in-chief (rotating? elected every three months?) to address the time-critical nature of the project. A completed issue would then be generated in several formats; on-wiki, PDF, etc. Maybe even go through proprietary distribution channels like Amazon or Apple, if the license situation allows it. I am sure tablet users would flock to it, and we might get some of these "consumers" to participate in one of the Wikimedia projects, maybe with "photos by readers" as an entry-level drug :-)
I'll answer these as one question. For tool developers, Labs is already a fine solution. There are a few rough edges which could be smoothed, though; "find someone on IRC" is often the way things are done, which is not always the best. There were a few outages recently, which can happen, and it took hours for someone to have a look a the issue, which is not exactly a life-or-death situation, but still frustrating for tool authors, and not just because of "your tool is broken" messages piling up around them. I understand that only core systems can have someone on standby 24/7, but maybe Labs issues could bubble up the chain automatically if no one from the usual Labs crew is around.
Getting more people to make use of the great Labs facilities is important. Part of that could be a simple visibility issue: if more people knew that Labs offers not only CPU and storage, but live mirrors of the Wikimedia databases, or that they could easily help fixing or improving that vital tool, we would probably see more widespread adoption of Labs by programmers. Labs-based git repositories for each tool could also enhance visibility, and improve code reuse (which I practice heavily within my own tools).
In terms of adoption of tools and extensions by volunteer developers into Wikimedia wikis, MediaWiki core itself, or as stand-alone systems, clear and time-limited review procedures would be required, as well as assistance by Wikimedia developers to get code up to MediaWiki standards. On the other end, a public listing with project ideas that, if implemented, would be considered for adoption by Wikimedia, could focus volunteer programmer participation. I am talking about a simple list of "we would like to have these, but don't have the manpower" issues, written by Wikimedia staff, as opposed to obscure feature requests in bugzilla that might be long obsolete.Open source is also to work together on software, tools. Your tools are available, how do we get more people to cooperate on them
By refusing to fix bugs, we could force the bug submitter to do it ;-)
On a more serious note, I think improving visibility, as mentioned above, of the great things Labs offers, and that participation on existing tools is encouraged and welcome. Just like many people use Wikipedia but still are not aware that they could edit it themselves, potential volunteer programmers might think that these tools are done by Wikimedia staff, or some carefully chosen group, rather than by run-of-the-mill geeks like them.When you had someone to work on improving ONE tool; what would you want him or her to do?
Extend Wiri a.k.a. "the talk page". It is not so much a normal, "useful" tool, but a nice technology demo, not just for Wikidata, but for a confluence of technologies (data from Wikidata, speech generation from third-party open source, speech recognition from Google) enables functionality that plays in the same ballpark as big commercial solutions like Siri or Google Now.
I am well aware it will never be en par with the Mathematica/Wolfram Alpha backend in terms of calculation power, or up-to-the-minute sports results. But even simple improvements, like a listing of options if the (speech) input is ambiguous (e.g. several people with the same name), translating complex questions into Wikidata query requests, displaying images, maps, or using AutoLists to show multiple results, could turn it from a mere demo into an actually useful tool. With proper, fault-tolerant grammar parsing, real reasoning, and the ability to explain the reasoning, it could be amazing!
Tuesday, October 29, 2013
Using #Babel should be obvious in #Wikidata
When you know multiple languages, you want to see the Wikidata labels used for the languages that are relevant to you.
My current list of languages is defined using the #Babel template on my user page. The syntax is:
Thanks,
GerardM
My current list of languages is defined using the #Babel template on my user page. The syntax is:
{{#babel:nl|en-4|de-3|fr-1|ar-0|id-0|jv-0|ase-0}}It makes a world of a difference when you are able to add useful labels in the languages you know. Added labels ensure that subjects can be found.
Thanks,
GerardM
Monday, October 28, 2013
Abdullah, King of #Saoudi Arabia
King Abdullah has many brothers and sisters. In #Wikidata he and his siblings are registered as children of his father. Different is that the Reasonator now shows them by querying the parents. It is no longer needed to register them as brother or sister on each brother and sister.
Thanks,
GerardM
The edits of #Wikidata II
The number of Wikidata edits are measured real time and hidden in the number of edits are the number of qualifiers added.
As there is a new set of statistics in town, their numbers are measured as well. Currently there are 23.176 qualifiers on statements. As you can see in the graphic, they are growing fast. So far there are no bots who add qualifiers.
When the bots know how to set qualifiers, it will make the available information more understandable and relevant to humans.
Thanks,
GerardM
As there is a new set of statistics in town, their numbers are measured as well. Currently there are 23.176 qualifiers on statements. As you can see in the graphic, they are growing fast. So far there are no bots who add qualifiers.
When the bots know how to set qualifiers, it will make the available information more understandable and relevant to humans.
Thanks,
GerardM
Sunday, October 27, 2013
John Sherman, #USA Secretary of State and of the Treasury
It is fun to check what #Wikidata has to say of people and places prominently mentioned in #Wikipedia. The article about Mr Sherman is a featured article. There is always something to improve and it is now registered that Mr Sherman had a father, a grandfather and several brothers. Sadly it does not register in the Reasonator.
Mr Sherman was part of the "Opposition party", this is an article that needs some serious attention. The article describes three instances of an Opposition party and this does not make sense in the context of Wikidata. From the article it was not clear when Mr Sherman moved to this party from the Whig and later to the Republican party.
Thanks,
GerardM
Mr Sherman was part of the "Opposition party", this is an article that needs some serious attention. The article describes three instances of an Opposition party and this does not make sense in the context of Wikidata. From the article it was not clear when Mr Sherman moved to this party from the Whig and later to the Republican party.
Thanks,
GerardM
Saturday, October 26, 2013
The edits of #Wikidata
![]() |
| "Right now the meter is standing on my fridge and is watched by a webcam" |
I really enjoy this image; I find that I go back to it. One of the implications earlier in the day was that in a month every Wikidata item may or may not get one edit.
Thanks,
GerardM
Raja Lumu, the first sultan of #Selangor
His father and son both have articles in one #Wikipedia. In all other Wikipedias they are red links. His son was his successor and second sultan of Selangor.
When a new article gets written on Ibrahim Shah of Selangor, it is a best practice to link this article to other articles. Given the existing links in articles to other articles, there is already a concept cloud for Raja Ibrahim Shah. This "concept cloud" will include his father, his successor and child among others.
With a bit of luck, these concepts have labels in Wikidata and when they have not, it makes sense to add them and get familiarised with them. All these concepts are likely to be used in the new article.
When the concepts known to exist for an item are available while editing an article, it makes sense to use them while editing the article.
When a new article gets written on Ibrahim Shah of Selangor, it is a best practice to link this article to other articles. Given the existing links in articles to other articles, there is already a concept cloud for Raja Ibrahim Shah. This "concept cloud" will include his father, his successor and child among others.
With a bit of luck, these concepts have labels in Wikidata and when they have not, it makes sense to add them and get familiarised with them. All these concepts are likely to be used in the new article.
When the concepts known to exist for an item are available while editing an article, it makes sense to use them while editing the article.
- editors become aware of relevant concepts
- editors are prompted to link to existing articles
- editors are prompted to add missing labels
Thanks,
GerardM
Friday, October 25, 2013
An unknown woman from #Indonesia, a picture from the #Tropenmuseum
The Tropenmuseum has provided us with a large collection of images from its collection. Within Commons these images are particularly relevant because there is so little available on the subjects covered by this collection.
Attribution to the GLAMs we are working with is vitally important. Providing an insight to how a collection is used determines subsidies.
As these images are by and large in a category, it is possible to use that category and accumulate data with it. GLAMorous informs about the number of articles using images in a category. Even more relevant is the BaGLAMa tool; this is where you find the number of page views for these images.
There is room for improvement; there is a template for the Tropenmuseum but it is not part of the data on most images from the Tropenmuseum. There are templates for creators like Isidore van Kinsbergen; they are not universally applied either.
When the data on images exists in a database, it will become much easier to combine data in many new ways. Adding the creator and institution templates prepares for the moment when these templates are populated with data from Wikidata.
Thanks,
GerardM
Attribution to the GLAMs we are working with is vitally important. Providing an insight to how a collection is used determines subsidies.
As these images are by and large in a category, it is possible to use that category and accumulate data with it. GLAMorous informs about the number of articles using images in a category. Even more relevant is the BaGLAMa tool; this is where you find the number of page views for these images.
There is room for improvement; there is a template for the Tropenmuseum but it is not part of the data on most images from the Tropenmuseum. There are templates for creators like Isidore van Kinsbergen; they are not universally applied either.
When the data on images exists in a database, it will become much easier to combine data in many new ways. Adding the creator and institution templates prepares for the moment when these templates are populated with data from Wikidata.
Thanks,
GerardM
The Gelman #Library, an institution in Washington DC
The Gelman library or by its full name the "Estelle and Melvin Gelman Library", is one of the many GLAMs we have content from in Commons. For all these institutions there is a template in the "Institutions" namespace.
All these templates are an amazing resource, it must have been compiled by many people over many years. On Commons it links to material that is known to be part of the collection of that institution. Making such links is in itself an Herculean job and one that is not finished at all.
The template on all those institutions typically refer to a Wikipedia article. The Wikipedia article links to a Wikidata item and it aims to include all the information that exists on the institution template on Commons. To harvest all that information tools like the pywikipedia bot will be used.
Some people complain about Wikipedia that "everything is said and done". For those people Wikidata is a bit of fresh air; there is so much more that can be done.
Thanks,
GerardM
All these templates are an amazing resource, it must have been compiled by many people over many years. On Commons it links to material that is known to be part of the collection of that institution. Making such links is in itself an Herculean job and one that is not finished at all.
The template on all those institutions typically refer to a Wikipedia article. The Wikipedia article links to a Wikidata item and it aims to include all the information that exists on the institution template on Commons. To harvest all that information tools like the pywikipedia bot will be used.
Some people complain about Wikipedia that "everything is said and done". For those people Wikidata is a bit of fresh air; there is so much more that can be done.
Thanks,
GerardM
Thursday, October 24, 2013
Manna Dey, a #singer from #India
Today Manna Dey died. He was really famous in India and #Bangladesh. When you want to know about Mr Dey, you will not find anything about him on Wikipedia when there is no article about him.
Realistically, you would not expect an article about him in the Occitan Wikipedia. Sadly, the Occitan Wikipedia cannot share the sum of all knowledge. To demonstrate that it could provide information after all, the following template was added:
What if the result of a "not found" was nicely formatted data from Wikidata?
Thanks,
GerardM
Realistically, you would not expect an article about him in the Occitan Wikipedia. Sadly, the Occitan Wikipedia cannot share the sum of all knowledge. To demonstrate that it could provide information after all, the following template was added:
{{Infobox Musica (artista)}}It resulted in an infobox with several missing labels in Occitan. They were added and the result is relevant information about Mr Dey on the Occitan Wikipedia. As you can see, they are red links for the Occitan Wikipedia.
What if the result of a "not found" was nicely formatted data from Wikidata?
Thanks,
GerardM
Subscribe to:
Posts (Atom)

























