Wikidata talk:Recoin

From Wikidata
Jump to navigation Jump to search

Delay in loading[edit]

I love the idea of this indicator but it taking forever to load. Any chance this can be improved / addressed? -- Erika aka BrillLyle (talk) 22:42, 6 December 2017 (UTC)

We are looking into it. I'll report soon! Ls1g (talk) 11:11, 7 December 2017 (UTC)
Thanks so much. I disabled it for now as it is slowing down editing Wikidata for me, but if you can ping me I would like to try to implement it again. Best, -- Erika aka BrillLyle (talk) 18:08, 7 December 2017 (UTC)
@BrillLyle: The slowness may be related to a general bug that was resolved over the weekend. Could you recheck whether the speed is satisfactory now? Ls1g (talk) 13:11, 11 December 2017 (UTC)
@Ls1g: Oh my -- yes the slowness is gone -- it's very speedy and works well. Very nice! Very satisfactory. Best, Erika aka BrillLyle (talk) 23:05, 11 December 2017 (UTC)

Offering contra-sex ids[edit]

For cyclists I see that where a female cyclist has CQ Ranking female cyclist ID (P2709) in pace in the identifiers, that it is suggesting that CQ Ranking male cyclist ID (P1541) is missing. Is that something that needs to be prevented on the property as a constraint, or is that something controlled within your options? See Vicki Whitelaw (Q19519519) for an example.  — billinghurst sDrewth 06:51, 9 December 2017 (UTC)

That looks like a tricky one! So far Recoin does not consider any constraints, but as it is, I do not even see any constraint preventing this on Property_talk:P1541. We do a little filtering on the class level, i.e., filter out things like date of death (P570) and image of grave (P1442) as otherwise they are suggested for all living humans, but the present case requires to look at values (gender). I take note of this case - do you see a way to formulate a constraint saying that female cyclists can't have CQ Ranking male cyclist ID (P1541)? Ls1g (talk) 14:51, 10 December 2017 (UTC)

Tools list update[edit]

This is great! I've added the screenshot, and updated the link at the WD:Tools page, but I wasn't sure whether to replace the instructions on how to install, with the (newer?) instructions from this page. Also, I suggest turning the old script location (User:Ls1g/recoin-core.js) into a redirect to the new location, so that anyone who is using that old version gets updated. Cheers, Quiddity (talk) 19:43, 12 December 2017 (UTC)

@Quiddity: Thanks for the update of the tool list, I had forgotten about that. I put now also the second variant there and updated the installation instructions. Regarding the redirect for the old script location, I attempted to create a redirect as per w:en:Wikipedia:User_pages#Deleting_your_user_page_or_subpages, could you maybe check whether I did it right? Ls1g (talk) 13:41, 13 December 2017 (UTC)
@Ls1g: I believe the way you've got it now, is correct. Thanks for the other fixes at the Tools page, and again for this whole feature! :) Quiddity (talk) 18:22, 16 December 2017 (UTC)

Translation[edit]

Thank you for this amazing tool! Is it possible to display the properties labels in the user main language? Tubezlob (🙋) 20:17, 2 January 2018 (UTC)

Thanks for the suggestion! We are working on this and will push the changes soon. Property labels will be translated automatically, few other strings can be manually translated here. Preview see picture on the right. Ls1g (talk) 16:18, 9 January 2018 (UTC)
Preview of multilingual version of Recoin
@Tubezlob:: Deployed now, should display everything in the language as defined in the user settings. Strings can be translated as per above, please let us know in case of any issues! Ls1g (talk) 16:54, 29 January 2018 (UTC)
Thank you for your work! Tubezlob (🙋) 20:40, 29 January 2018 (UTC)

Add statement[edit]

Would it be possible to add "addstatement" function (already at User:Vvekbv/recoin.js) to gadget version as well?--Jklamo (talk) 23:25, 19 January 2018 (UTC)

Yes we want to do that - gadgets can only be edited by admins, we contacted one and are waiting for a reply. I'll let you know when the gadget is updated. Ls1g (talk) 22:25, 23 January 2018 (UTC)
@Jklamo: Now added for all Wikibase properties. Please let us know in case of any issues. Ls1g (talk) 16:56, 29 January 2018 (UTC)
@Ls1g: Already noticed (and used). I have not noticed yet any issues. Thanks for implementation! --Jklamo (talk) 17:00, 29 January 2018 (UTC)

Newbie questions[edit]

Question: How is Property:P1853 "Blood type" on this list, is that relevant (or even desirable) information for most people? I keep running into this editing musicians and pop stars ;) Moebeus (talk) 00:07, 29 January 2018 (UTC)

It's based on the usage on Wikidata. The information is mostly present on Korean and Japanese artists. Sjoerd de Bruin (talk) 10:08, 29 January 2018 (UTC)

Invalid SQL query[edit]

After loading TER Lisboa Expresso (Q9081217), this is reported in the console:

SyntaxError: missing ; before statement

Further details reveal a possible bug in the backend:

Cannot execute query: SELECT pid2, count, probability FROM wikidatawiki_p.wbs_propertypairs WHERE (pid1, qid1) IN ) and pid2 not in (127,127) order by probability desc limit 50

Matěj Suchánek (talk) 19:20, 29 January 2018 (UTC)

Thanks for pointing that. This scenario was because there was no available data that Recoin could produce for the item TER Lisboa Expresso (Q9081217). We were using that to debug certain scenarios, now I have changed the output to print "No data available" text instead.--Vvekbv (talk) 21:26, 29 January 2018 (UTC)

Should not suggest constraint violations[edit]

In the "Most relevant properties which are absent" section, some of the suggested "relevant" properties are occasionally properties that would be constraints violations. I think it would be better if Recoin did not suggest that editors add such properties. --Yair rand (talk) 16:16, 6 February 2018 (UTC)

Also noticed and I agree, that it would be better if Recoin did not suggest these.--Jklamo (talk) 09:11, 8 February 2018 (UTC)
Thanks for the comments, do you know of generic way to check whether a property would create a conflict? I looked at some examples and it looks like it could be challenging to implement all checks from scratch. Also I wonder how strict all these constraints are: CQ Ranking female cyclist ID (P2709) demands via conflicts-with constraint (Q21502838) that no CQ Ranking male cyclist ID (P1541) is present - makes sense. But what about the constraint that CQ Ranking female cyclist ID (P2709) requires sex or gender (P21)? That looks less necessary, should that be enforced too? Is there a core subset of constraints, e.g. only conflicts-with constraint (Q21502838) that one should focus on? Ls1g (talk) 14:03, 8 February 2018 (UTC)
How about type constraint (Q21503250)? I think that would be the most relevant. --Yair rand (talk) 22:14, 14 February 2018 (UTC)

Bug?[edit]

Something weird going on on Jan Jonker (Q47500903), stays on least complete. Sjoerd de Bruin (talk) 08:20, 8 February 2018 (UTC)

Thanks for reporting, the problem was that both of his professions had each only two instances. So easily 50% to 100% of the comparison entities had some properties that Jan Jonker (Q47500903) did not have (the dropdown list should have shown those). We changed the computation now so that we only compute occupation-specific completeness if there are at least 50 or 200 (exact to be yet determined) entities having that occupation, otherwise completeness will be calculated wrt. general humans (also not ideal as now it asks for sport-related properties, as sportsmen make up a significant share of the general humans, but at least completeness is at second highest level now). Ls1g (talk) 14:16, 8 February 2018 (UTC)

Raise the bar for researchers?[edit]

The occupation researcher (Q1650915) doesn't really have hard targets, see for example Feiko ter Kuile (Q37606371). Sjoerd de Bruin (talk) 12:09, 14 February 2018 (UTC)

After some rethinking, it would look weirdly. Ignore this. Sjoerd de Bruin (talk) 15:28, 18 February 2018 (UTC)

Ignore dissolved, abolished or demolished (P576) and replaced by (P1366) per same reasoning as date of death (P570)[edit]

See Hunze en Aa's (Q14941974) for some example, this is because the majority of the items classified as water board in the Netherlands (Q702081) are former entities. Sjoerd de Bruin (talk) 15:27, 18 February 2018 (UTC)

@Sjoerddebruin: The properties dissolved, abolished or demolished (P576) and replaced by (P1366) are now treated same as date of death (P570). So they would not be suggested by Recoin.--Vvekbv (talk) 09:56, 5 March 2018 (UTC)
Thank you! Sjoerd de Bruin (talk) 09:56, 5 March 2018 (UTC)

Recoin & qualifiers[edit]

Not sure if Recoin looks at qualifiers & their absence; if not, might this be something to think about? I note this thread on Project Chat, which if it is not trying to reinvent Recoin in another form, might be asking for something which I read as roughly Recoin dealing with qualifiers. --Tagishsimon (talk) 01:23, 27 April 2018 (UTC)

Extension[edit]

Is there the way to extend list (about 5 or 10 more positions or add second table on the right with next 10 positions) with missing properties? Eurohunter (talk) 18:05, 10 February 2019 (UTC)

@Eurohunter:. By default Recoin shows a maximum of 10 properties. You can access more properties using the https://tools.wmflabs.org/recoin/getmissingattributes.php?lang=en&subject=Q15074414&n=100 where n is the number of properties you would like to see. Unfortunately, the gadgets do not have a user preference setting specific to each gadget, so for now it is not included in the default gadget. Hope this is useful. --Vvekbv (talk) 16:56, 12 March 2019 (UTC)
@Vvekbv: Link doesn't works anymore? Eurohunter (talk) 20:11, 18 June 2019 (UTC)

Outage[edit]

The tool does not work for me for a few days. Any plans to fix it?--Jklamo (talk) 21:20, 23 March 2019 (UTC)

@Jklamo:. Apologies for the issue. This has been fixed now. --Vvekbv (talk) 07:07, 25 March 2019 (UTC)
Thanks, works again.--Jklamo (talk) 16:11, 25 March 2019 (UTC)

Hello, Recoin seems out again... no icon, and the menu for top missing properties does not deploy when clicking on it. Thanks for looking at it, please :) --Hsarrazin (talk) 09:16, 18 June 2019 (UTC)

@Hsarrazin:. Apologies for the inconvenience. We are working on fixing this issue and Recoin should be up as soon as possible. --Vvekbv (talk) 07:49, 19 June 2019 (UTC)
thanks ! this was brought to my attention by a new GLAM contributor who just installed it, and thought they'd done some mistake ;) --Hsarrazin (talk) 07:51, 19 June 2019 (UTC)
@Hsarrazin:. The issue has been fixed now. Thank you for notifying it. --Vvekbv (talk) 14:45, 19 June 2019 (UTC)

Stuck[edit]

Recoin is stuck @ Q6262560 :( --Hedwig in Washington (talk) 10:10, 5 November 2019 (UTC)

Hi @Hedwig in Washington:. Could you please explain on the issue. I notice that it works fine from my end. --Vvekbv (talk) 12:04, 6 November 2019 (UTC)
The indicator didn't change color, now it works again. Thanks for having a peek. :) Hedwig in Washington (talk) 00:02, 7 November 2019 (UTC)

Source code?[edit]

Hello!

Apologies if I missed it, but I was curious about the source-code of the recoin tool − is it available somewhere?

Thanks! Jean-Fred (talk) 14:00, 26 November 2019 (UTC)

Hi @Jean-Frédéric:, thanks for your interest in Recoin. The database from which Recoin gadget loads the suggestion can be found under section "Data Dumps". For more details please reach me at balaraman@fbk.eu, I would be happy to provide further details. --Vvekbv (talk) 10:15, 27 November 2019 (UTC)

Avoid encouraging populating the gender field for living people[edit]

I think it would be wise to either completely avoid encouraging the population of the sex or gender property for living people, or to at least show a warning reminding people of the living people policy and cautioning not to populate that property without a reliable source. Asaf Bartov (talk) 14:03, 20 February 2020 (UTC)

Hi @Ijon:, Thanks for bringing this to our attention. We have pushed an update to recoin that filters the gender property in the suggestion..--Vvekbv (talk) 16:09, 24 February 2020 (UTC)

Faster recognition[edit]

Hello,

I would like "Most relevant properties" (above the Labels) to go faster in its recognition. There are properties that are only used in certain cases. For example, using ISAN (P3212), we are sure to know what it is about. The addition of duration (P2047), director (P57), etc. become essential.

Best regards. —Eihel (talk) 07:45, 12 May 2020 (UTC)