Would it be possible to set the language used to search with? Whilst I most often use English on Wikidata I'm sure a lot of people don't.
/André On 14 Feb 2016 22:03, "Markus Kroetzsch" <markus.kroetz...@tu-dresden.de> wrote: > On 14.02.2016 18:03, Hay (Husky) wrote: > >> On Sun, Feb 14, 2016 at 4:40 PM, Markus Kroetzsch >> <markus.kroetz...@tu-dresden.de> wrote: >> >>> I suspect that https://query.wikidata.org can count how many times each >>>> property is used. >>>> >>> >>> >>> Amazingly, you can (I was surprised): >>> >>> >>> https://query.wikidata.org/#SELECT%20%3FanyProp%20%28count%28*%29%20as%20%3Fcount%29%0AWHERE%20{%0A%20%20%20%20%3Fpid%20%3FanyProp%20%3FsomeValue%20.%0A}%0AGROUP%20BY%20%3FanyProp%0AORDER%20BY%20DESC%28%3Fcount%29 >>> <https://query.wikidata.org/#SELECT%20%3FanyProp%20%28count%28*%29%20as%20%3Fcount%29%0AWHERE%20%7B%0A%20%20%20%20%3Fpid%20%3FanyProp%20%3FsomeValue%20.%0A%7D%0AGROUP%20BY%20%3FanyProp%0AORDER%20BY%20DESC%28%3Fcount%29> >>> >> That's a really nice find! Any idea how to filter the query so you >> only get the property statements? >> > > I would just filter this in code; a more complex SPARQL query is just > getting slower. Here is a little example Python script that gets all the > data you need: > > > https://github.com/Wikidata/WikidataClassBrowser/blob/master/helpers/python/fetchPropertyStatitsics.py > > I intend to use this in our upcoming new class/property browser as well. > Maybe it would actually make sense to merge the two applications at some > point (the focus of our tool are classes and their connection to > properties, as in the existing Miga tool, but a property browser is an > integral part of this). > > Markus > > > _______________________________________________ > Wikidata mailing list > Wikidata@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikidata >
_______________________________________________ Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
