[07:16:24] nikki: yesterday was it you who asked for a tool suggesting properties? Did you see http://tools.wmflabs.org/wd-art/human/ or http://tools.wmflabs.org/wd-art/joconde/ ? [07:16:32] if it's not you, sorry [07:19:38] not really, I was looking for a way to influence the property suggester [07:20:08] (well... to tell it to always show me certain properties until I tell it to stop doing it :P) [07:20:56] nikki: seems like everyone want something like that and everyone try to implemente it differently [07:23:12] yeah... when you're working on a particular topic, there are often certain statements or properties you want to use a lot, so it doesn't surprise me [07:23:41] exactly [07:24:45] it's particularly annoying for new properties, the suggester won't suggest them until you use them enough but you can't use them easily (without other tools) until it starts reliably suggesting them >_< [07:36:23] WikidataFacts: https://www.wikidata.org/wiki/Q283543 does this looks good for glass specification? [07:36:31] Still don't know how to indicate "on the rocks" [07:38:00] sjoerddebruin: looks good, I can’t think of anything better either [07:41:10] is “on the rocks”, in the widest possible sense, a “genre”? [07:41:31] That would be property abuse [07:41:35] yeah [07:41:43] I've created https://www.wikidata.org/wiki/Q26876981 though [07:41:57] oh good [07:43:34] what about this? https://www.wikidata.org/w/index.php?title=Q283543&type=revision&diff=376117434&oldid=376117171 [07:44:09] sjoerddebruin: I approve this edit [07:44:15] not bad [07:44:39] but not sure if the different usage of “use” and “as” makes sense here [07:44:59] hmmm [07:45:18] particularly – if it still makes sense in all translations of those two fairly general words [07:45:31] could also use https://www.wikidata.org/wiki/Property:P518 for the glass [07:46:02] and use https://www.wikidata.org/wiki/Property:P366 for on the rocks and garnishes [07:46:03] hm, that would be similar to paintings (applies to part: painting surface) [07:47:03] i'm happy with the current display [07:47:40] can you add this to the query? [07:49:13] gotta go now, sorry [07:49:20] but I’ll try to add it later [07:49:56] okay <3 [09:34:00] hm, the ingredients get doubled if I add references to them :/ [10:24:16] harmonia: do you know we have a property for "alternative"? There are a lot of cocktails with "X or Y" [10:25:16] no idea, sorry [12:13:29] DanielK_WMDE: Hey, I have some questions regarding https://phabricator.wikimedia.org/T144923 [12:14:03] tell me when you have some time [12:35:55] Amir1: hey [12:37:37] DanielK_WMDE: firstly, I want to get some advice on which type of special page we need [12:37:53] QueryPage? [12:38:23] It seems it can't handle sub pages in URL but everything is there already [12:38:24] probably. QueryPage isn't super nice, but it's made for queries that generate lists of page titles, which is exactly what we do [12:38:33] you also get all the paging stuff for free [12:38:40] so yea, I'd try that and see how it goes [12:39:06] thanks. [12:39:11] the downside is: you can't share code between the special page and wbentityusagelist. would be nice to do that, since they implement the same logic [12:39:55] but... well, the query is pretty trivial, and if QueryPage makes it easy to implement, I'd say use that for now [12:40:34] DanielK_WMDE: the problem is that we can't have Special:EntityUsage/Q123 [12:40:36] Amir1: QueryPage doesn't support Special:Foo/Bar? [12:40:42] let me check [12:40:43] nope [12:42:18] Amir1: ok, here'S a hack: [12:43:00] public function execute( $par ) { $this->entity = $par; parent::execute( $par ); } [12:43:26] or $this->entity = $this->idParser->parseId( $par ) or something [12:43:39] okay, I get the idea [12:44:13] thanks [12:44:15] np [12:44:28] and what about when someone checks Special:EntityUsage [12:44:47] I don't think there is a way to give a nice form [12:45:13] but meh. https://en.wikipedia.org/wiki/Special:Diff [12:46:30] Amir1: sure, you return the HTML for the from from getPageHeader [12:47:21] Okay, I will check it [12:47:22] Amir1: have a look at SpecialPagesWithBadges [12:47:31] nice [12:47:45] hm... maybe you can also subclass PageQueryPage... not sure what that gains you though [12:48:11] DanielK_WMDE: It formats the link [12:48:17] ah, yea, it does link formatting and prefetching of page info [12:48:26] but I think I should skip that because we want to add aspects, etc. [12:48:35] you can use that, though you might want to add aspect info somehow. [12:48:55] I would prefer to show only one page per result row though. aspects can be comma-separated. [12:49:49] Amir1: you can still use PageQueryPage, override formatResult() and call parent::formatResult inside, then add the aspect string. [12:50:17] otoh, PageQueryPage isn't a lot of code. you could just copy the link batch stuff to your class. [12:50:29] but using LinkBatch is probably a good idea. [12:52:48] okay [12:53:59] so I try using PageQueryPage and if it doesn't work out very well. I switch to QueryPage [12:55:58] sjoerddebruin: Want to help out? https://www.wikidata.org/wiki/User:Josve05a/dupes :p [12:57:33] Josve05a: can do a few, want to finish my cocktails though [12:58:01] Currently done all people born later than 1994-01-19 [12:59:37] sjoerddebruin : you drunkard ! [13:00:08] I'm already seeing double, Alphos. [13:01:02] As I said, the cocktail query shows double values when they are referenced (WikidataFacts) [13:03:18] sjoerddebruin GROUP BY and (SAMPLE() AS) [13:03:35] PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 11.11% of data above the critical threshold [300000.0] [13:04:07] Alphos: que? [13:05:26] sjoerddebruin show me your query ^^ [13:05:48] https://twitter.com/WikidataFacts/status/775495442352185346 [13:08:46] RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0] [13:13:18] Lydia_WMDE: any update on duplicatereferences? I miss it so much. [13:13:31] sjoerddebruin: i have pushed it into the current sprint [13:13:42] so hopefully the devs look at this soon [13:21:42] Alphos: little bit complicated? [13:42:32] This heat... And all the shifting content on http://iba-world.com isn't helping either. [13:44:39] sjoerddebruin nah, was grabbing something to eat ^^' [13:45:34] sjoerddebruin so which ones are duped ? [13:45:45] the ingredients [13:45:55] "6 centiliter carbonated water, 6 centiliter carbonated water" [13:46:53] oh [13:48:07] what property should be used for creation date of cocktails? [13:48:08] SELECT ?cocktail ?cocktailLabel (GROUP_CONCAT(DISTINCT ?ingredient; separator=", ") AS ?ingredients) # concatenate all ingredients together, separated by comma [13:48:11] ;-) [13:48:54] I’m working on an improved version btw [13:49:02] w00t [13:49:03] \o/ [13:49:58] I'm using https://www.wikidata.org/wiki/Property:P61 for the creator of the cocktail, is that correct? [13:50:03] sjoerddebruin have you tried with GROUP_CONCAT(DISTINCT) ? [13:50:22] Alphos: i'm still a sparqlnoob [13:50:47] sjoerddebruin SELECT ?cocktail ?cocktailLabel (GROUP_CONCAT(DISTINCT ?ingredient; separator=", ") AS ?ingredients) # concatenate all ingredients together, separated by comma [13:50:51] * harmonia like "sparqlnoob" :p [13:50:56] replace your first line with this, and you're good :) [13:51:24] yeah, I did that [13:53:49] what are your opinions about the latest three statements? https://www.wikidata.org/wiki/Q745306 [14:04:54] sjoerddebruin what about them ? [14:05:14] well, i've added a new one now... are they correctly for a cocktail? [14:06:33] they seem right conceptually [14:06:39] no idea if the values are right [14:08:28] I’m running into some very strange OPTIONAL behavior… does anyone know if this result is correct? http://tinyurl.com/jaj8lo6 [14:09:52] Alphos: that's all I wanted to know :) [14:18:36] well, I’m getting the same results on several other endpoints, so apparently… not a bug :( [14:30:26] erm, I also seem to have started a query that doesn’t time out (DESCRIBE) [15:00:50] DanielK_WMDE: One strange question, I see array() syntax in wikibase a lot. Why haven't we migrated? Just curiosity :D [15:01:28] now I’m getting this error from WDQS: “ERROR: Could not contact server” [15:04:08] WikidataFacts: I'm checking ... [15:04:28] it works if I make the query slightly shorter [15:04:49] and the error is back if I just add a long comment [15:05:03] is there some sort of length limit on the query? perhaps in the caching layer? [15:05:35] WikidataFacts: there is certainly some limit, not sure how large it is... [15:05:52] query has 3546 chars [15:06:42] 3462 works [15:07:19] I see a few errors that seem related to the memory needed for the query [15:07:39] WikidataFacts: could yo upastebin your query somewhere? [15:08:03] gehel: http://tinyurl.com/jt64w3e this one’s still slightly below the limit [15:08:24] adding nine more characters (comment) pushes it over [15:08:36] interesting... [15:09:54] WikidataFacts: this is more involved than what I actually understand... I just deployed a minor change to the blazegraph startup script and was afraid this was a consequence, but it looks unrelated [15:10:29] alright, should I file a ticket? even if the limit is intentional, the way it’s presented to the user is far from ideal IMO [15:10:35] WikidataFacts: you'll need someone who understand all this better than I do... [15:14:35] Amir1: just because we never did. would be nice to make a concerted effort at some point. [15:15:11] The sooner the better I guess [15:15:35] I'm about to finish early parts, the SpecialPagesWithBadges was super useful [15:15:57] Amir1: cool. i'm about to give the api modulea final review [15:16:09] awesome, thanks [16:34:33] hi [16:34:35] who is [16:34:37] there [16:34:54] hello [16:35:10] any one here ? [16:42:13] no [16:43:10] well, there could have been [17:04:44] Please tell me I added these correctly... https://www.wikidata.org/w/index.php?title=Property_talk:P3151&diff=376161457&oldid=375740325 [17:17:19] when you want to tweet a query, and twitter tells you the link is too long, and tinyurl gives you 502 Bad Gateway… q_q [17:18:15] WikidataFacts: tried goo.gl ? [17:18:28] tinyurl works now, I guess it was just a hiccup [17:36:35] Lol [17:37:01] !admin [17:37:26] Please don't abuse that command, thanks. [17:37:37] !admin [17:54:07] maybe he needed an admin... [17:56:24] hey, anybody remembers which page lists wikidata version deployments? like https://www.mediawiki.org/wiki/MediaWiki_1.28/Roadmap but for wikidata. There was one IIRC but I don't remember where [17:57:02] https://www.mediawiki.org/wiki/Wikidata_deployment seems dead too [17:59:17] sjoerddebruin: that's the one, thank you! [17:59:30] but yes, seems not updated anymore [17:59:37] yeah, sadly [17:59:52] SMalyshev: I think wikidata would go in group 1 [18:00:12] in the "a few other sites" statement [18:00:13] Platonides: the question is if the tags are the same [18:00:23] because wikidata has a lot of its own code [18:18:25] SMalyshev: trivial fix : https://gerrit.wikimedia.org/r/#/c/310364/ [18:18:43] SMalyshev: if you have a second to review anyway... else I'll just merge [18:19:16] done [18:23:16] thanks! [18:28:34] SMalyshev: and finally it works! At least on eqiad. [18:29:36] gehel: great! [18:35:59] SMalyshev: loadData is finally running on wdqs200? I think that this time we are good for real! Pfff... [18:37:05] Is there a property for http://www.calflora.org/ ? [18:46:45] Well, now there is a proposal for it at least https://www.wikidata.org/wiki/Wikidata:Property_proposal/Calflora_ID [19:27:43] hello [19:28:30] you will all bleed [19:34:50] hoo: hey! [19:58:21] some cocktails lack photos, this ask for a cocktail bar at the wikidata party :P [19:59:01] sjoerddebruin: obviously [19:59:45] Let's start with https://www.wikidata.org/wiki/Q70428