In the mean time, other games are doing well. Given that #Wikipedia is the centre of attention, it is an improvement that other languages also exist and get attention from official WMF research.
This long-standing bias of no official attention means that "it"[1] does not really exist because "it" is not officially studied and therefore "it" is not considered.
"It" however attracts so many people that it gets mentioned in the Guinness book of records. "It" could also be something a researcher calls "some of the most exciting things to happen in Wikimedia wikis in a long time".. "It" did not happen in a Wikimedia wiki as it is not a wiki.
What is studied is what it takes to attract new volunteers for Wikipedia. People who are willing and able to help us "share in the sum of all knowledge". That IS an aspiration. What we can achieve is "share in the sum of all available knowledge". That will not be delivered in any Wikipedia as we know it.
Thanks,
GerardM
[1] "it" is not defined because it could be so many of the bright things happening in the Wikimedia ecosystem.
Saturday, May 31, 2014
Friday, May 30, 2014
The #MediaWiki #GeoData extension is a #dinosaur
"This extension adds a new parser function, {{#coordinates:}}, that saves coordinates to the database. Function's input format is made as compatible as possible with GeoHack".
What it does is save data for one Wikipedia article at a time. It links it to another dinosaur, GeoHack, and hopes for best results..
For as long as such dinosaurs are aliveish and kicking, it may be good. At the same time, it provides an excellent target for harvesting all this geo-data and include it in Wikidata. That will make the same geo-data available to all articles in any Wikipedia on the same subjects.
GeoData saves its data to "the" database, when it decides to evolve and store its data in Wikidata, it may have some future after all.
Thanks,
GerardM
What it does is save data for one Wikipedia article at a time. It links it to another dinosaur, GeoHack, and hopes for best results..
For as long as such dinosaurs are aliveish and kicking, it may be good. At the same time, it provides an excellent target for harvesting all this geo-data and include it in Wikidata. That will make the same geo-data available to all articles in any Wikipedia on the same subjects.
GeoData saves its data to "the" database, when it decides to evolve and store its data in Wikidata, it may have some future after all.
Thanks,
GerardM
Monday, May 26, 2014
#Wikidata - the game
With the Wikidata Game, Magnus did it again. He created a few games that are quite compelling. In a few days the games have generated more than 100,000 edits in Wikidata.
It is awesome. Many people make a big job light. We now know about 1,964,351 humans, this is up from 1,332,383 on April 20th. We know about 1,459,421 males, up from 760,616 and 260,521 females, up from 154,455.
When a game makes a difference in only a few days, it follows that making a game out of our issues will provide us with quick results. As important, it grows awareness of Wikidata, it shows people that we need their help and the numbers prove that games work.
The question is not only if people are interested in making games but as much if they find it in themselves to cooperate and produce more, better and integrated games.
Thanks,
GerardM
It is awesome. Many people make a big job light. We now know about 1,964,351 humans, this is up from 1,332,383 on April 20th. We know about 1,459,421 males, up from 760,616 and 260,521 females, up from 154,455.
When a game makes a difference in only a few days, it follows that making a game out of our issues will provide us with quick results. As important, it grows awareness of Wikidata, it shows people that we need their help and the numbers prove that games work.
The question is not only if people are interested in making games but as much if they find it in themselves to cooperate and produce more, better and integrated games.
Thanks,
GerardM
Sunday, May 25, 2014
#Wikidata - Brazilians who died in 2014
How many people from Brazil died in 2014 according to Wikidata. The answer is obvious when you know that a human is a Brazilian. So when he dies, ie a date of death is available, it is just a matter of applying the right query and you get an answer.
Surely there are more than 41 notable Brazilians who died in 2014. It means that we need to know for more humans that they are Brazilian. The category Naturais do Brasil knows about some 26,520 Brazilians, 1,128 are not known to Wikidata and 14,393 are known to be human. Of these humans 7,481 are known to be Brazilians and consequently we can safely add a statement of a Brazilian nationality to 6,912 humans.
This process is under way and the number of deaths is on the rise. Not as much as you would expect because nationality is often added when someone is registered as dead.
What is left are 1,128 articles that need an item and 12,127 items that need to become both human and Brazilian.
Thanks,
GerardM
Surely there are more than 41 notable Brazilians who died in 2014. It means that we need to know for more humans that they are Brazilian. The category Naturais do Brasil knows about some 26,520 Brazilians, 1,128 are not known to Wikidata and 14,393 are known to be human. Of these humans 7,481 are known to be Brazilians and consequently we can safely add a statement of a Brazilian nationality to 6,912 humans.
This process is under way and the number of deaths is on the rise. Not as much as you would expect because nationality is often added when someone is registered as dead.
What is left are 1,128 articles that need an item and 12,127 items that need to become both human and Brazilian.
Thanks,
GerardM
Saturday, May 24, 2014
#Wikimedia-#Labs its script kiddies and its public
Labs is the home of many tools. These tools are often essential to workflows or they show people information that they cannot get in any other way. When you want to work on people who died in 2014, you use this script. When you want to have information about 土门岭村, a village in China, you use Reasonator.
Labs has three types of public; there are the heroes who develop tools, there are the people who use these tools to generate more data and there are the consumers of all the information that becomes available.
They all have one thing in common. For them to function Labs has to be operational.
When Labs is not always available, when the quality of service suffers, the tools will not get the exposure they seek. Script kiddies will not generate more data and the public will not share in the information that should be available to them.
Thanks,
GerardM
Labs has three types of public; there are the heroes who develop tools, there are the people who use these tools to generate more data and there are the consumers of all the information that becomes available.
They all have one thing in common. For them to function Labs has to be operational.
When Labs is not always available, when the quality of service suffers, the tools will not get the exposure they seek. Script kiddies will not generate more data and the public will not share in the information that should be available to them.
Thanks,
GerardM
Friday, May 23, 2014
#Wikidata - statement #statistics
The Wikidata statistics can be bewildering. Above you find a comparison of the last two dumps. You would expect that statements are added and that the number of items with more statements only grow. This time it is not the case. Yes, the total number of statements has gone up but the decrease of the number of items with 6, 7, 8 or 9 statements is more than the increase of the number of items with 10 or more statements.
The good news is that the number of items with no statements has gone down significantly.
Thanks,
GerardM
Thursday, May 22, 2014
When #Google is my friend; translating from #Marathi
I am adding dates of death to many people who died in 2014. Included in my workflow are people with an article on the Marathi Wikipedia. It is well known that translating into Marathi for articles is not great. For my purpose; identifying a date of death and a date of birth it is good enough :)
Thanks,
GerardM
#Wikidata - Jaime Lusinchi, president of Venezuela
Yesterday Mr Lusinchi died. Thanks to a ToolScript this was noticed. It was found that Wikidata was not aware that he was president of Venezuela.
Currently he is the only Venezuelan president where information is included like when he became president and who preceded him. For many if not all of the others Wikidata is now at least aware that they held the office of President of Venezuela.
Thanks,
GerardM
Currently he is the only Venezuelan president where information is included like when he became president and who preceded him. For many if not all of the others Wikidata is now at least aware that they held the office of President of Venezuela.
Thanks,
GerardM
#Wikidata - Conflict of interest
Wikidata has many objectives and the one thing that makes Wikidata relevant is that from the start it is there to be used. The most important use cases for Wikidata are:
- repository of interlanguage and interproject links
- depository of data that may provide information in Wikimedia projects
There is an inherent conflict. In order to be a depository of data, all articles need an item in Wikidata. For a complete set of interlanguage and interproject links items on the same subject are not acceptable.
This issue becomes even more problematic when external use of Wikidata is to be considered as well.
Wikidata is immature and it shows. When its problems are to be solved, more and better tools are needed. These tools will need room to evolve and most of all, the people who are involved in Wikidata need to talk with each other.
Thanks,
GerardM
Tuesday, May 20, 2014
Authorising #oAuth in Widar
Tools like AutoList and Reasonator get a boost from their ability to apply changes to Wikidata. Reasonator shows labels in the languages you know and missing labels in your language can be added. AutoList enables you to add multiple statements to items that it shows in a list.
This is powerful stuff. It helps when you understand how it works. Widar is the tool that does handle the authorisation for oAuth. It remembers the authorisation by using cookies. These cookies are associated with your browser. When you use multiple browsers, you have to authorise multiple times.
As Reasonator is used everywhere, people will authorise often. As the cookies persist, it is important to end the authorisation for Widar. The functionality to do so has been added recently.
Thanks,
GerardM
This is powerful stuff. It helps when you understand how it works. Widar is the tool that does handle the authorisation for oAuth. It remembers the authorisation by using cookies. These cookies are associated with your browser. When you use multiple browsers, you have to authorise multiple times.
As Reasonator is used everywhere, people will authorise often. As the cookies persist, it is important to end the authorisation for Widar. The functionality to do so has been added recently.
Thanks,
GerardM
#Wikipedia vs #Wikidata - a qualitative comparison
When a Wikipedia thinks it knows something, and Wikidata begs to differ, what to do? Wikidata has its information from a different source or someone actually looked it up or someone made a booboo. It is all possible and someone has to look into it. This is where sources become actually relevant.The thing to do is actually pretty simple. You research it or you report it. For a bot that is looking for specific facts, reporting is the obvious way to go.
Two reports by Amir show the differences for the date of birth and the date of death between the English Wikipedia and Wikidata. By highlighting these issues, it becomes possible to raise quality in both Wikidata and Wikipedia.
At this time these reports are generated for a first time. Some false positives have been found. The location of these reports is not optimal and, the communities of Wikidata and English Wikipedia are not yet aware.
Reporting on problems however is one obvious way of raising quality. It is hopefully the first of many similar reports.
Thanks,
GerardM
Sunday, May 18, 2014
#Wikipedia - an alternative to #bots
What bots do is generate text from the data that is provided to them using an algorithm. When you have a lot of data, it will create a lot of text or a lot of articles. When data is added at a later date, the text of a bot generated article will not change. Typically an article is served from a cache.
As bot generated articles are a bad idea when they are in a fixed format, why should we have them? That is, why not generate them when they are requested and serve them from a cache, just like any other article.
Typically, the data of a bot generated article can be provided by Wikidata and Commons. Scripts that generate articles already exist. What is needed is to import the data in Wikidata and generate the text when requested. The number of articles will go down and this is actually a good thing. It means that the articles left are the ones that humans have edited, are involved in.
So what we need are some people with language skills to create the scripts for all the languages we support. We need the WMF engineers to consider articles on demand and think through how such an article gets into the caches and statistics. We need to inform our communities about what people are reading and where a human touch can bring such articles to the next level of quality.
Thanks,
GerardM
As bot generated articles are a bad idea when they are in a fixed format, why should we have them? That is, why not generate them when they are requested and serve them from a cache, just like any other article.
Typically, the data of a bot generated article can be provided by Wikidata and Commons. Scripts that generate articles already exist. What is needed is to import the data in Wikidata and generate the text when requested. The number of articles will go down and this is actually a good thing. It means that the articles left are the ones that humans have edited, are involved in.
So what we need are some people with language skills to create the scripts for all the languages we support. We need the WMF engineers to consider articles on demand and think through how such an article gets into the caches and statistics. We need to inform our communities about what people are reading and where a human touch can bring such articles to the next level of quality.
Thanks,
GerardM
#Wikidata - Mukesh Gadhvi, used to be a member of the 15th Lok Sabha
Mr Gadhvi died in 2013. What makes him interesting is that there were two articles about him on the English Wikipedia. Both have him represent the Banaskantha electoral district in Gujarat. That article made it obvious that he died and was succeeded by Mr Haribhai Parthibhai Chaudhary.
Like so many members of the Lok Sabha, Mr Gadhvi had a father who was also into politics. Given that it provides more information, an item for Mr B.K. Gadhvi was created as well.
NB For many if not most members of the Lok Sabha, there is no picture yet. The pictures is from the obituary you can find with Google.
Thanks,
GerardM
Like so many members of the Lok Sabha, Mr Gadhvi had a father who was also into politics. Given that it provides more information, an item for Mr B.K. Gadhvi was created as well.
NB For many if not most members of the Lok Sabha, there is no picture yet. The pictures is from the obituary you can find with Google.
Thanks,
GerardM
Thursday, May 15, 2014
#Wikidata - 2014 deaths
In the many #Wikipedias, articles for people who are notable or noted indicate their demise. The deaths of 2014 are registered in Wikidata. Adding the deaths from the Ukraine Wikipedia is rather depressing. Then again, if the death of the people who died in the Ukraine is not noted, they may have died in vain.
Thanks,
GerardM
Wednesday, May 14, 2014
#Wikidata - duplicate items
In the Matrix, every duplicate will fight you. In Wikidata you may kill of every duplicate. This is done by merging them. The result is good; statements are combined, articles are combined in the oldest item of the two.
Merging is easiest using the merge gadget. There are loads of duplicates, there could not be as much as 20% doubles .
A first tool to attack this multitude is the "Wikidata duplicate item finder". Based on the assumption that everything has an unique name you will get a list with many possible doubles. With this tool Magnus very much provides a first tool to fight the agent Smiths of Wikidata. Other tools are needed; for instance to look for a combination of labels and date of birth.
Thanks,
GerardM
Merging is easiest using the merge gadget. There are loads of duplicates, there could not be as much as 20% doubles .
A first tool to attack this multitude is the "Wikidata duplicate item finder". Based on the assumption that everything has an unique name you will get a list with many possible doubles. With this tool Magnus very much provides a first tool to fight the agent Smiths of Wikidata. Other tools are needed; for instance to look for a combination of labels and date of birth.
Thanks,
GerardM
Tuesday, May 13, 2014
#Wikidata - the 3th earl of Mayo
Joseph Deane Bourke, 3rd Earl of Mayo has a Wikipedia article. It is largely filled with his genealogy and his ecclesiastic career.
Wikidata used to know him as a "list of" "person". An automated process added "instance of" "human" to Mr Bourke. These two claims are obviously mutually exclusive. Thanks to AutoList it is possible to find the items that have both claims.
At this stage you have to remove the wrong claim one at a time in Wikidata itself. The automated process operated on the presumption that an entry in a category that is named like "1794 deaths" are humans. As can be expected, this is mostly true.
Thanks,
GerardM
Wikidata used to know him as a "list of" "person". An automated process added "instance of" "human" to Mr Bourke. These two claims are obviously mutually exclusive. Thanks to AutoList it is possible to find the items that have both claims.
At this stage you have to remove the wrong claim one at a time in Wikidata itself. The automated process operated on the presumption that an entry in a category that is named like "1794 deaths" are humans. As can be expected, this is mostly true.
Thanks,
GerardM
Monday, May 12, 2014
Tom Kettle, a UK MP
Preparations are under way for edit-a-thons about the great war. The objective is that more quality information becomes available that can be associated with World War I.
As I am waiting for a plane home, I am adding images to humans who can be found in the category British Army personnel of World War I. The tool I use is WD-Fist and, this is a perfect way to wait, idling.
Many of the people who fought in World War I died. When you look at their images, they were so young. The ones with an article have to be notable in one way or another. Mr Kettle died at the Somme. He volunteered to fight, he was not the only MP who died.
Thanks,
Gerard
As I am waiting for a plane home, I am adding images to humans who can be found in the category British Army personnel of World War I. The tool I use is WD-Fist and, this is a perfect way to wait, idling.
Many of the people who fought in World War I died. When you look at their images, they were so young. The ones with an article have to be notable in one way or another. Mr Kettle died at the Somme. He volunteered to fight, he was not the only MP who died.
Thanks,
Gerard
#WMHack #Maps and #Wikidata II
This hackathon had many people with an interest in maps come together in Zurich. There were several challenges they faced; how to represent maps in a wiki, how to store them and what do we need to know about them in Wikidata. In this mix of challenges the differences between contemporary maps and historic maps feature as well.
Wikidata needs to know several specific things; it needs to know that something is a map, it needs to know the four corners of a map, the location where that map can be found and finally it is nice to know what type of map it is. More attributes are possible but this was considered the minimum for Wikidata.
The thought process about Commons was forward looking; it is going to be "Wikidatafied" and this will surely affect current practices. Information that is currently in templates will move into Wikidata and many of the galeries and categories will surely become redundant because queries will provide a more reliable and complete result.
For Wikis, current best practices were analysed and, it was found that information on a map exists in many layers. There is a base layer and on top of that you can show a contemporary or historic map. On top of it you may want to show the shapes of countries or districts. These may be sprinkled with pointers that reflect the result of a query. To finish it off, you may want to add even more that demonstrates a point made in a particular article.
All this information needs a place. It needs a special place because you may want to use a map several times. In Zurich we ended of a working example of a map that included all these complications by inserting information in a namespace. The next challenges are to make it robust and user friendly enough.
Thanks,
GerardM
Wikidata needs to know several specific things; it needs to know that something is a map, it needs to know the four corners of a map, the location where that map can be found and finally it is nice to know what type of map it is. More attributes are possible but this was considered the minimum for Wikidata.
The thought process about Commons was forward looking; it is going to be "Wikidatafied" and this will surely affect current practices. Information that is currently in templates will move into Wikidata and many of the galeries and categories will surely become redundant because queries will provide a more reliable and complete result.
For Wikis, current best practices were analysed and, it was found that information on a map exists in many layers. There is a base layer and on top of that you can show a contemporary or historic map. On top of it you may want to show the shapes of countries or districts. These may be sprinkled with pointers that reflect the result of a query. To finish it off, you may want to add even more that demonstrates a point made in a particular article.
All this information needs a place. It needs a special place because you may want to use a map several times. In Zurich we ended of a working example of a map that included all these complications by inserting information in a namespace. The next challenges are to make it robust and user friendly enough.
Thanks,
GerardM
#WMHack - #Wikidata and bias towards English #Wikipedia
English Wikipedia has more articles, it has loads of info boxes. As importantly most of the people importing data know English and consequently a lot of data is imported into Wikidata from that source. According to some it must be that Wikidata is biased because information available in the English Wikipedia is better represented..
Uhm, a great argument. Lets analyse that. The current statistics show that 50% of all Wikidata items have zero or one statement. They typically refer to only one article and, have only one label. Effectively it is garbage wherever it originated from. That leaves us with the other half. Less than one in thirty has 10 or more statements and for less than one in fifteen we have ten or more labels. Only a fraction of the subjects covered by the English Wikipedia has great information.
We assume good faith when we say that the English Wikipedia aims to share in the sum of all knowledge AND aims to provide a neutral point of view. It is easiest to retrieve information from the en.wp and when we add all that to Wikidata, we gain the most improvement in quality for the least amount of effort for most of us. Even then, it is surprisingly problematic to set up the effort to get data in. It takes time and an inordinate amount of bickering before data finally finds its place.
When you look at all that data once it found its place, you find that Wikidata itself looks best in English. As long as fall back languages for statements are not supported, its information looks reasonable only when seen in the Reasonator.
Wikidata aims to be a quality resource for information. When all it has is information from the English Wikipedia, you might as well go to the English Wikipedia. When Wikidata gets its house in order and compares its information with many sources and reports on the differences found, it helps improve information everywhere and reduces the existing bias.
When those sources include multiple Wikipedias, it will be biased towards those it compares with.
Thanks,
GerardM
Uhm, a great argument. Lets analyse that. The current statistics show that 50% of all Wikidata items have zero or one statement. They typically refer to only one article and, have only one label. Effectively it is garbage wherever it originated from. That leaves us with the other half. Less than one in thirty has 10 or more statements and for less than one in fifteen we have ten or more labels. Only a fraction of the subjects covered by the English Wikipedia has great information.
We assume good faith when we say that the English Wikipedia aims to share in the sum of all knowledge AND aims to provide a neutral point of view. It is easiest to retrieve information from the en.wp and when we add all that to Wikidata, we gain the most improvement in quality for the least amount of effort for most of us. Even then, it is surprisingly problematic to set up the effort to get data in. It takes time and an inordinate amount of bickering before data finally finds its place.
When you look at all that data once it found its place, you find that Wikidata itself looks best in English. As long as fall back languages for statements are not supported, its information looks reasonable only when seen in the Reasonator.
Wikidata aims to be a quality resource for information. When all it has is information from the English Wikipedia, you might as well go to the English Wikipedia. When Wikidata gets its house in order and compares its information with many sources and reports on the differences found, it helps improve information everywhere and reduces the existing bias.
When those sources include multiple Wikipedias, it will be biased towards those it compares with.
Thanks,
GerardM
Sunday, May 11, 2014
#WMHack #Maps and #Wikidata
This hackathon and many maps put #Zurich on the map. When you consider maps and, particularly historic maps, they have four corners and a date. That is the minimal approach to a map. You can add to this what a map intends to show, it can be a thematic map or a generic map.
When you add the four corners of a map as properties to a map, you can query for the maps that include Zurich.. When the maps are dated, you can show them in order..
It is really exciting that it has been decided what we need in a map on Wikidata.
Thanks,
GerardM
When you add the four corners of a map as properties to a map, you can query for the maps that include Zurich.. When the maps are dated, you can show them in order..
It is really exciting that it has been decided what we need in a map on Wikidata.
Thanks,
GerardM
Subscribe to:
Posts (Atom)

.jpg)














