Hi Brill, Great you like the idea! Regarding speed, unfortunately the current delay is unavoidable when the indicator is based on live data. There appears to be a conflict between being up-to-date (-> live computation) and being fast (-> precomputation), we'll look whether there is a way to have fast, maybe via triggers on changes. Cheers, Simon On 6 December 2017 at 23:45, Brill Lyle <wp.brilllyle(a)gmail.com> wrote:

On Thu, Dec 7, 2017 at 7:50 PM, Brill Lyle <wp.brilllyle(a)gmail.com> wrote: Yeah something wonky is going on. Investigation is happening here: https://phabricator.wikimedia.org/T182322 Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Product Manager for Wikidata Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

On 10 December 2017 at 10:41, Gerard Meijssen <gerard.meijssen(a)gmail.com> wrote: As quick reply I would say don't shoot the messenger :-). If Recoin finds that some of the most important Indonesian national heroes are less well documented than some minor league Baseball players then....that is firstly food for thought. I agree though that labels like "basic information" and red symbols can create an unintended negative perception, but I have no idea how to do it differently (albeit from lowering the thresholds). It could indeed be that many of the red items are already very useful as they are, yet, who could decide this and create necessary annotations? Thus the idea of Recoin is to show a *relative* completeness/informativeness based on how much is known about other, similar entities. helps to improve things? An expandable list of things to improve should be loaded directly below the page title (unless it is pushed down by other plugins/scripts)? for an entity with the entity's Recoin completeness indicator? Thanks for the interesting analysis! Yes, there should be some positive correlation, yet the way we compute the indicator (look at avg frequency of top 5 missing properties) it is much more important that the frequent properties are there, than that many are there in general. This is not scientifically grounded though (I am not aware of any scientific work discussing how one should compute such indicators), so what we compute is a simple heuristic, and we are glad for any suggestions for different computation. Cheers, Simon

On 10 December 2017 at 10:51, Egon Willighagen <egon.willighagen(a)gmail.com> wrote: If there's consensus that that is preferred we could definitely change it. We have in fact discussed that idea earlier with the WD UX team, the current behaviour, linking to a generic page, is how status indicators on behave on WP, so creates coherence. But linking to the absent properties would indeed also make a lot of sense, unfortunately the two choices are exclusive, so any thoughts on what is better are appreciated! Cheers, Simon