[00:27:03] why is there no way to order stuff like "population" https://www.wikidata.org/wiki/Q104994 [00:28:07] well, anything that has multiple values over time is currently a mess in wikidata [06:28:11] PROBLEM - puppet last run on wdqs1006 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): File[/usr/local/bin/prometheus-puppet-agent-stats] [06:58:41] RECOVERY - puppet last run on wdqs1006 is OK: OK: Puppet is currently enabled, last run 4 minutes ago with 0 failures [11:48:44] SothoTalKer: probably because there are always other things to implement or fix that seem more important [11:49:26] like the totally important lexeme stuff :-p [11:50:31] and I get impression that the wikidata ui is not really seen as something that needs to be really cool, the important thing is the data because as long as we have data other people can build cool things [11:51:39] if you do not wish that this data is editable by humans in a nice why, why bother displaying it at all. [11:53:32] my point is that someone could write something to display (and even edit) population data nicely without having to wait for the wikidata devs to implement it [11:53:47] whereas it's much harder for other people to do things like that if wikidata doesn't support it [11:55:45] I'm not saying that's my opinion necessarily, that's just the impression I get [11:56:13] I'm a bit ambivalent about it, attempts to make things "nicer" usually end up more annoying for me :P [11:56:37] it's not a thing for population data only. any data that is sortable is just mangled in the order it was added. Another thing: normal statements are ordered nicely, where identifiers have a random order (: [11:56:55] there was a discussion about identifiers recently [11:58:37] ah, I'm thinking of https://www.wikidata.org/wiki/Wikidata:Requests_for_comment/Sort_identifier_statements_on_items_that_are_instances_of_human [11:59:15] why limit it to humans? [11:59:41] I didn't start the page :P [12:00:38] anyway there was some discussion in there about sorting by identifier label (which isn't possible right now) and manually sorting by english label instead (which seems fine to me as a temporary option if the plan is to eventually fix it) [12:01:30] (where "manually" means listing all of the properties in the page where the order is listed) [12:02:20] the person who started the page really wants viaf first, but I don't like that idea [12:03:20] i can understand that the person wants it first. it's the most widely used authority identifier. [12:04:02] that doesn't mean it's the best or most useful though [12:04:29] anyway I wrote my reasons on that page [12:05:11] yes, i saw them :-) [12:05:32] if people want certain properties first, it's possible to add a few lines to your common.js to do that... I do that for the things that are useful for me :) [12:07:47] there's that, but I don't know how to apply it XD https://www.wikidata.org/wiki/MediaWiki:Wikibase-SortedProperties [12:35:41] Alphabetic still sounds best for me. [12:36:04] Or make it that you can pin properties that they appear first on every item. [12:36:54] And I would love identifiers suggestions seperate (and always show the external ID-section, bad UX choice) and influenced by P106. [12:40:47] * nikki really doesn't want identifier suggestions separate :/ [12:40:55] I'd rather get rid of one of the add links instead [12:42:37] I don't think about whether I'm adding an identifier or not, I just add everything in whatever order I find it [12:43:03] I suppose it doesn't help either that I use the keyshortcuts thing, I rarely *click* the add button, I just press "a" [12:44:04] nikki: maybe only P106 will better the situation [12:44:14] now useful properties for sports people are burried under viaf and other things [12:44:55] maybe only P106? [12:45:03] the influence thing [12:45:33] If P106 > soccer player boost identifiers that are used on items with that. [12:51:46] in the suggestions? yeah, that'd be nice [13:00:10] soccer players (: