[00:29:01] ^ found his answer [07:52:48] ayuda con coordenadas del item https://www.wikidata.org/wiki/Q16557867 [10:56:10] hoo: i'm getting quick at writing RFCs :) https://phabricator.wikimedia.org/T114640 [10:56:53] DanielK_WMDE: already have patches for that but definitely want an rfc and some broader input [10:57:07] it's all a bit scary :o [11:58:09] Hey, In this edit: hash of the reference has changed. Is it intentional? If it is, is there anything consistent (like GUID in claims) to distinguish between changing a ref. and adding and removing ref. [11:58:21] https://www.wikidata.org/w/index.php?title=Q7251&diff=254947223 [12:31:52] aude: Hey :) ^ [12:40:45] Can anyone help with this? [12:40:48] Lydia_WMDE: [12:41:42] Amir1: not me, sorry. maybe hoo [12:42:04] okay :) [12:45:28] Offhand: No, I don't think there's anything stable in references [12:50:55] okay :) [12:51:00] Thanks [13:15:21] aude: the usage tracking tool seems borked :( it shows the exact same number of total usages as 2 weeks ago. can you maybe give it a kick? [13:21:17] Lydia_WMDE: it doesn't track over time [13:21:52] but can see about doing that [13:22:16] aude: but it should change the current vlaue no? [13:22:19] *value [13:22:31] i have the tracking of that value in my spreadsheet from 2 weeks ago [13:22:56] and both times it says 153598782 [13:23:01] it doesn't update [13:23:10] oh? [13:23:14] hmmm [13:23:19] if i update it, then would like to store the old values also [13:23:30] hmmmm ok [13:23:40] is there a way i can get the total value for today? [13:23:46] for my stats [13:23:48] let's see [13:24:07] DanielK_WMDE: https://phabricator.wikimedia.org/T69122 [13:24:55] * aude is struggling to find vegetarian things to eat here :( [13:31:22] aude: Do you know why the property parser function uses Parser target language, but Lua doesn't? [13:33:29] hoo: no [13:33:42] Ok [13:33:50] ideally, lua would do the same thing [13:34:08] No, it wouldn't [13:34:11] We just changed it [13:34:14] mw.wikibase.label() [13:34:20] we not? [13:34:20] so that Lua uses the user language if on multilingual wikis [13:34:27] and content language otherwise [13:34:29] aude: i remember we discussed unifying the code for determining the target language... was that only for the different bits of the parser function? I thought that also covered the Lua use case [13:34:40] That's what Parser::getTargetLanguage should return [13:34:44] in a perfect world [13:35:01] I think I remember reviewing the code that you wrapped around Parser::getTargetLanguage... did I dream that? [13:35:02] DanielK_WMDE: for both [13:35:29] there are patches for core [13:35:48] but didn't we have a workaround for wikibase? [13:35:59] basically, just a placeholder for the "real" method in core? [13:36:30] DanielK_WMDE: not yet... i would not want to touch lua, unless it was sufficiently announced that we are changing how it works [13:37:34] I just did that, but it will depend on the setting [13:37:40] so that we can carefully announce [13:37:46] but not sure what to do with the parser function [13:39:14] hoo: i would not change the parser function [13:39:35] if someone uses {{int:}} on a page, e.g. for translate, then the page is user language [13:39:36] 10[1] 04https://www.wikidata.org/wiki/Template:int: [13:39:41] he [13:40:58] aude: Ok [13:41:06] In that case my patch is complete [13:41:11] hoo: link to the patch? [13:41:25] One sec [13:41:38] if {{int:}} gets used, ideally lua would also be user lang [13:41:39] 10[2] 04https://www.wikidata.org/wiki/Template:int: [13:41:44] based on target language [13:41:46] here you go: https://gerrit.wikimedia.org/r/243645 [13:41:52] * aude kicks the bot [13:42:00] aude: uh... {{int:}} doesn't change what getTargetLanguage returns, does it? [13:42:01] 10[3] 04https://www.wikidata.org/wiki/Template:int: [13:42:34] aude: it seems to me that the parser function currently can't be used for content localized in the user's interface language. [13:42:35] DanielK_WMDE: it does [13:42:38] o_O [13:42:49] that seems extremely broken. it's completely backwards. [13:42:52] afaik, that's how commons has the cache split [13:43:23] aude: yes, it splits the cache, but afaik it doesn't change wgat getTargetLanguage returns. these two things are apparently unrelated. which is part of the problem [13:43:33] i think it changes both [13:43:57] that's so scary :( [13:47:56] parser is so scary [13:55:26] * hoo rages [13:55:41] That stuff is just insane [13:56:04] now i am not sure [13:56:14] I'm testing it right now [13:56:23] and don't really understand the behvaiour yet [13:56:23] we probably want to unify this code [13:56:36] e.g. https://www.wikidata.org/wiki/User:Aude/test [13:56:37] We want to just fix Parser::getTargetLanguage [13:56:52] hoo: would be better [13:57:13] if i use uls to choose spanish, then purge, it still says "Cat" [13:57:40] if i did things "correctly" with int [13:58:38] Lydia_WMDE: when do you need the updated stats? [13:58:57] That's what I see locally as well [13:59:12] * aude apparently confused [13:59:40] aude: today would be great but tomorrow is also ok [13:59:47] if possible [13:59:50] Lydia_WMDE: ok, maybe later [13:59:53] k [14:00:21] Lydia_WMDE: aude: going to update the suggester today, to reflect the changes caused by units [14:01:06] cool [14:01:13] hoo: \o/ [14:01:42] * aude needs to run and maybe there is working wifi on the trains here [14:03:41] ok, cu [14:44:13] What is the best way to describe numeric intervals on Wikidata? [14:44:25] For example, if I have a range of measurements that are valid. [15:06:58] in some cases we have separate properties for the minimum and maximum, but if that doesn't work, I don't really know [15:10:59] Would it be reasonable to propose properties for upper bound and lower bound? [15:11:10] as qualifiers for another property? [15:27:43] We have those for dates, so why not numbers... [15:50:24] indeed! [15:50:31] and it would reduce the need to create two properties for the same thing [16:05:30] Seems like a good idea. The range stuff has bothered me for months and coincidently I posted this today: https://www.wikidata.org/wiki/Wikidata_talk:Development_plan#Ranges.2C_Arrays.2C_Maps [16:06:23] We need some kind of intermediate solution until the developers have time to build more complicated datatypes. [16:06:38] And a qualifier is at least something we can improve right now. [16:06:38] hoo: Can you also take a look why we don't have entity suggestions on properties? [16:08:01] hm... don't we have a bug for that [16:08:08] Guess that would be a bit of work [16:08:10] Can't remember. [16:08:44] Unless you say that you don't care and want to throw them together with items, then it might be quite easy [16:09:01] Meh, think that doesn't help. [16:14:52] I'm wondering what's the most popular property with units. [17:00:12] Hi. how can I get a list of article in wikidata linked to just one language and created by just a specific person. I'm looking for articles creted by someone without interwiki in wikiar [17:07:12] tobias47n9e, sjoerddebruin: I created proposals. https://www.wikidata.org/wiki/Wikidata:Property_proposal/Generic#upper_bound https://www.wikidata.org/wiki/Wikidata:Property_proposal/Generic#lower_bound [17:07:33] Helmoony: It is possible, but I don't think there is a easy way. Maybe you should add a request to the bot requests page. [17:08:21] harej: great! [17:10:01] I haven't found something usefull in toolserver tools [17:11:07] Yup, it's not a very usual thing. [17:22:26] harej: Thanks for the ping. Will comment. [17:59:37] harej: Maybe it could also work as item-datatype "boundary measurement" --> "lower boundary" or "upper boundary" as qualifier to the value. [18:03:30] Perhaps though I would like it to work under as many circumstances as possible [18:59:56] A fun thing to do: Listen to Wikidata, especially when the bots are out. http://listen.hatnote.com/#wikidata [19:00:47] Lydia_WMDE: ^ that should so be music at the event at the office :P [19:43:03] Lydia_WMDE: Why don't you just have an on wiki list at https://www.wikidata.org/wiki/Wikidata:Third_Birthday/Party so everyone can see who is coming? [21:07:12] DanielK_WMDE: How long should https://ca.wikipedia.org/w/index.php?title=Minneapolis_Institute_of_Art&type=revision&diff=15847929&oldid=15847926 take on Wikidata to register? [21:08:24] Less than 30s [21:08:32] but it can take up to 30m if you're unlucky [21:10:03] multichill, hoo: i don't see a wikidata link in the sidebar. which item should the page be connected to? [21:10:32] https://www.wikidata.org/w/index.php?title=Q1700481&action=history [21:10:34] Ah, there it is [21:10:40] 4 minutes. Hmm [21:11:11] depends on job queue size [21:11:26] Yeah... delayed jobs are a little unpredictable, still [21:11:35] that as well, but that is not really a problem usually [21:12:09] Related https://phabricator.wikimedia.org/T97909 [21:12:48] Ah, just a bit confusing. Happy to see that it does work, just a bit slower than expected [21:13:07] It's quite stable nowadays :) [21:14:48] People at https://www.wikidata.org/wiki/Q1700481 decided it was a good plan to drop the s in the name so now it's the Minneapolis Institute of Art [21:19:29] hoo: https://www.wikidata.org/w/index.php?title=Q1700481&action=history <- hmm, a bot seems to be in the way [21:20:32] Yeah, can be that bots are faster [21:20:43] but we can't really do anything about that [21:20:51] delayed jobs are just not predictable :S [21:21:12] * hoo wishes we didn't need such bots [21:21:23] I mean... I even run one that checks sitelinks :P [21:22:24] I moved the remaining sitelinks. Let's see how long that takes. Time for bed [21:24:11] good night