[08:16:37] https://meta.wikimedia.org/w/index.php?title=Talk%3AWikimedia_Foundation_website%2F2017_update&type=revision&diff=17228397&oldid=17124725 [08:20:42] Nemo_bis: I've definitely heard people complain about how the current WMF site isn't multilingual so it will probably be considered [08:21:27] harej: you should perhaps add your assumption to that talk page to make sure it's aligned with the reality of the process :) [10:47:49] Hi guys, how do we query Wikidata items containing certain property? [10:53:12] Have you tried the query assistant of https://query.wikidata.org? [11:06:18] Hello folks [11:07:05] Hi! [11:07:08] I got a question concerning a special WD-mistake [?] [11:08:09] Hmmm special [11:09:45] Lydia_WMDE: https://www.wikidata.org/wiki/User:Lucas_Werkmeister_(WMDE)/External_identifiers [11:10:00] some articles of Websoftware (including a template using "actual version" data fom wikidata) i.e. de:Doctrine (PHP) showing an ref-Error. [11:10:31] sjoerddebruin, Yes I am trying sprawl query [11:11:10] But not getting a way to query if in an item, coordinate location property exist or npt [11:17:43] anyone got an idea [12:02:21] leszek_wmde: Die you forgot to merge this? https://github.com/wmde/WikibaseDataModelSerialization/pull/222 [16:00:41] Hello! I'm wondering how to build a query to get all data of human anatomy with its hierarchy. I tried this one http://tinyurl.com/ybtppwwl but # It does not return, for example, Kidney (Q9377), Liver (Q9368) nor Heart (Q1072). Is there a way to get those data? [16:06:43] floatingpurr: interesting! [16:06:58] i'm not familiar at all with the way these things are modelled in Wikidata [16:07:32] neither do I : ) [16:07:36] i remember playing once with a tool that displayed the shortest path between any two identifiers in DBpedia (but I can't find it anymore) [16:07:53] it would be nice to have the same thing for wikidata, maybe it would help in a case like this [16:09:03] absolutely! It would be nice having a clear way to extract data. :,( [16:11:27] oh I found it: http://www.visualdataweb.org/relfinder.php [16:12:16] floatingpurr: well, human knowledge is complex, so the data model is complex, so you need a complex query interface... [16:12:36] it make things simple, you'd need a tool that is build for a specific use case. [16:12:49] there are quite a few of thouse [16:17:04] floatingpurr: I think the problem is that some organs are makred as boing part of mamals or vertrebrates, not humans specifically. [16:17:32] floatingpurr: so you would have to search for all things that are part of humans or of any class that human is a (direct or indirect) sublcass of [16:20:30] floatingpurr: http://tinyurl.com/ydze4nat [16:20:36] better? [16:21:19] i still don't see heart, though. and i see duplicates. hm. [16:23:36] pintoch: great tool [16:24:33] DanielK_WMDE_: it seems better but it seems there is a clear pattern to follow to get human body parts :/ [16:25:30] floatingpurr: yea. inconsistent modeling is a problem. the only way to tackle it is for people to realize, care, collaborate, and fix it [16:26:17] floatingpurr: i recommend posting on the talk page here: https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Anatomy [16:26:30] oh wait, that's the wikipedia project, not wikidata. [16:26:34] well, you can ask there, too :) [16:27:31] floatingpurr: this exists, but seems dead: https://www.wikidata.org/wiki/Wikidata:WikiProject_Anatomy [16:27:39] better try https://www.wikidata.org/wiki/Wikidata:WikiProject_Medicine [16:27:57] DanielK_WMDE_: I am trying to use wikidata ad hub for life-sciences annotation of lab experiments. According to your experience it could be reliable? When I see the problems with this simple query, I feel pessimistic [16:28:52] Yep, DanielK_WMDE_ Medicine seems more active. [16:29:02] floatingpurr: i'm an expert for the software that runs wikidata, not so much for the content :) [16:29:13] in general, the statements you find on a wikidata item tend to be correct, but incomplete [16:29:45] similarly, sets you find using queries will generally not contain (much) false hits, but may be missing some or even most entries. [16:30:09] Neat... [16:30:10] and, as you found out, in some areas the modeling is inconsistent. [16:30:37] yep : ( I agree [16:31:03] wikidata is like wikipedia... stuff is here if someone put it here. the modelign is nice if someone made it nice [16:31:40] it's an experiment in large scale collaborative ontology modeling. as far as i can tell, we are on the right traqck, but it takes time to settle [16:33:59] Very clear DanielK_WMDE_ thank you! [16:34:29] I'll try to post my question in Medicine and in queries request section [16:35:21] :D [16:37:41] ? [16:37:43] :p [16:37:58] Just positive about all things going on here. [16:41:27] me too :) [16:42:06] even if I'm a newbie [18:03:51] Aleksey_WMDE: Reminder - https://phabricator.wikimedia.org/T170515 / https://gerrit.wikimedia.org/r/#/c/370300/ [18:46:35] PROBLEM - Blazegraph Port on wdqs1003 is CRITICAL: connect to address 127.0.0.1 and port 9999: Connection refused [18:46:36] PROBLEM - Check systemd state on wdqs1003 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [18:47:35] RECOVERY - Blazegraph Port on wdqs1003 is OK: TCP OK - 0.000 second response time on 127.0.0.1 port 9999 [18:47:36] RECOVERY - Check systemd state on wdqs1003 is OK: OK - running: The system is fully operational [21:46:39] whoa, I hate it when major properties get renamed. So confusing. [21:46:48] (e.g. P248, "stated in" until very recently. [22:02:57] hawke1: the old name is usually around as an alias, no? [22:25:23] harej: it is, it's just confusing to suddenly have it show up differently as I'm searching. [22:27:37] Would also be nice to be able to find out why something suddenly changed like that.