EloBot

Dead people playing chess ?

Please note the discussion at Property talk:P1087. In the meantime, I think it's preferable to stop adding more of them. --
--- Jura 07:23, 29 October 2016 (UTC)

Can you fix it and continue afterwards. Thanks.
--- Jura 07:56, 5 November 2016 (UTC)

(@Jura1:) See also last reverts by בורה בורה in Leonid Gofshtein (Q2036425). It doesn't seem to be right to fill it for dead people. This should be fixed in all those people: (tinyurl: yc4ufr2d)

SELECT DISTINCT ?person ?personLabel
WHERE
{
    ?person wdt:P570 ?dead.
    ?person p:P1087 ?rating .
    ?rating pq:P585 ?ratingT .
    FILTER(?ratingT > ?dead).
	SERVICE wikibase:label {
		bd:serviceParam wikibase:language "en" .
	}
}
GROUP BY ?person ?personLabel

Eran (talk) 16:15, 5 January 2018 (UTC)

Thanks Eran. I was about to report it, just was not sure where. בורה בורה (talk) 16:22, 5 January 2018 (UTC)

Eran, בורה בורה: This topic was extensively communicated in the above mentioned property discussion. Wesalius (talk) 14:17, 7 January 2018 (UTC)

You are right, but I see that there is no consensus there of having rating after death. Eran (talk) 12:56, 8 January 2018 (UTC)

There is no new information since then - the bot was approved to add elo ratings from FIDE database, it is publicly available, you can look up the ratings yourself. At the time of the addition the admins were noticed - MultiChill joined the mentioned discussion, I agreed to add the deprecated rank to ELO statements of players after death after the import is done. Import is not done yet. Wesalius (talk) 15:01, 8 January 2018 (UTC)

Thank you for the explanation, deprecated rank could be another good way to handle it. What do you mean (technically) by "after the import is done"? I think it would be better to patch the bot earlier (e.g before further imports), to avoid need to rerun/resync the rank. (you can use elo_claim.setRank(...) [1] for this). Eran (talk) 23:09, 8 January 2018 (UTC)

Was this mentioned in the proposal?
--- Jura 15:35, 8 January 2018 (UTC)

The proposal is public. You can look it up. Wesalius (talk) 15:42, 8 January 2018 (UTC)

The bot proposal mentions the Zombie part? The property proposal doesn't.
--- Jura 15:51, 8 January 2018 (UTC)

Bot proposal is public as well. Wesalius (talk) 16:00, 8 January 2018 (UTC)

This issue was not known by the time of proposal, therefore it was not mentioned. You attracted admins attention to the whole topic and no action was taken if I recall. Lets stop this pointless repetetive discussion here, you are moving in circles. Wesalius (talk) 15:58, 8 January 2018 (UTC)

Eran brought it up and the way I read your answer, I understood that it was agreed beforehand (which seemed odd). It appears that more and more people are concerned by approach taken by this bot. (see following thread as well).
--- Jura 16:05, 8 January 2018 (UTC)

On the other hand there has been multiple calls from people to get the latest elo ratings updated since they would like to include those in player infoboxes, use the data in player performance graph visualizations etc. I wont stop adding elo statements upon your request as I did not stop before. I encourage you (again) to stop posting here and act in some other way that is more productive. I wont respond here further. Wesalius (talk) 16:11, 8 January 2018 (UTC)

The workaround is to exclude items with P1087 from queries. The size of the data tends to crash some applications.
--- Jura 15:35, 8 January 2018 (UTC)

There is a consensus on adding elo statements, removing/deprecating after death ratings (which this discussion is about, again) wont make a big difference in app performance. Wesalius (talk) 15:42, 8 January 2018 (UTC)

For users that aren't interested and see their queries fail, just adding FILTER NOT EXISTS { ?item wdt:P1087 [] } avoids saturation.
--- Jura 15:54, 8 January 2018 (UTC)

Massive amount of Elo importations

Let's take an item, any item, that has the property Elo rating (P1087). This item: Lothar Schmid (Q63926)   .

Look at the amount of Elo rating properties it has. In fact, there are so many ratings to the point that the item is near unnavigable.

You can barely load the item, because of the excessive properties.

I think you should lower the amount of ELO rating properties. --PokestarFan • Drink some tea and talk with me • Stalk my edits • I'm not shouting, I just like this font! 17:50, 26 June 2017 (UTC)

I have loaded the item just fine and have no problems navigating it, it actually has only one elo rating statement, but with multiple values added.

How would you choose which value to delete? The values are all significant and might be reused in different wikiprojects - for example in this template.

I invite you to make further suggestions/open a discussion at Wikidata talk:WikiProject Chess Wesalius (talk) 15:32, 29 June 2017 (UTC)

Pokerstar, please stay at your poker stuff and don't make silly suggestions. Steak (talk) 07:44, 3 July 2017 (UTC)