Once a user publishes an article, the next step is normally to add the language links (i.e., link to equivalent articles in Wikidata). That is some manual step that can be automated.
We need to check whether the legal terms the user accepts when translating cover their contributions to Wikidata in order to be able to do so in the user's behalf.
This was reported at https://www.mediawiki.org/w/index.php?title=Topic:S6w7xbz00oie9c9t&topic_showPostId=sa6xct4j7tq0rea6#flow-post-sa6xct4j7tq0rea6
"Normal" prio; it's an important feature, but arguably less urgent than breaking bugs.
I don't see the concern here. There is no protectable interest in merely the fact that this article is a translation of the other article, so no one needs to consent to it being added to the database.
(But I may be missing something - I'm not sure I completely follow the relevant workflow.)
Thanks a lot for the quick reply, @LuisV_WMF!
The workflow is quite simple:
I just tested it, and there is no legal text in the Add links dialog, and based on that I'd assume that no legal text will be needed in our workflow.
@Lydia_Pintscher, anything to add?
Sounds good to me, too.
Are you covering the case when there is no Wikidata item yet?
Before you write any actual code here, feel free to contact me or someone else from the team. I have worked on similar things before and am probably able to show you what we already got, depending on how you actually want to implement this (server side vs. client side etc.).
@hoo, thanks for offering help.
I plan to work on it this week.
The scenario goes more or less like this:
Till here everything is already implemented. Step 4 is backend; everything else is frontend.
What this task wants to do is to add da:Aase_Birkenheier as a sitelink to https://www.wikidata.org/wiki/Q18601567 without any more interaction with the user. In case of Aase Birkenheier, a Wikidata item already exists, but it's also possible that one doesn't exist yet, so it will have to be created. Functionally, it is supposed to be very similar to what happens when the user runs the "Add links" tool, the entry point to which appears in Wikipedia after the interlanguage links list, but without any user interaction at all, because we already know that the newly created Danish page corresponds to the Danish one.
Given the above, should it be a step at the end of the backend cxpublish API? Or maybe a separate step initiated by the frontend after cxpublish finishes? Or something else?
Tips, opinions, examples, etc. - all welcome.
@santhosh, @Nikerabbit - you are welcome to chime in as well, of course.
Hi, I don't have a lot of time today (actually I'm not working the whole week and next week), but I still want to give some initial ideas. You can do it in the front end and make use of https://github.com/wikimedia/mediawiki-extensions-Wikibase/blob/master/client/resources/wikibase.client.PageConnector.js (that's what the Add links dialog uses) or you can make use of the wblinktitles api https://www.wikidata.org/w/api.php?action=help&modules=wblinktitles (that module can't perform item merges, but I guess that's not an issue here).
Using that api is probably the easiest and most stable thing to do. Binding against the Wikibase extension in PHP is probably not that much of a good idea given that we don't really have stable PHP interfaces.
Thanks!
ContentTranslation is developed mostly with Wikipedia in mind, but doesn't forget non-Wikimedia sites. What would be the right way that the current site is a Wikibase client? Check that $wgWBClientSettings is defined?
Server side we're using defined( 'WBC_VERSION' ) for this... on the client (JavaScript), you would probably check for the existence of the RL modules.
I think we just need wblinktitles api
api.php?action=wblinktitles&fromsite=enwiki&fromtitle=Hydrogen&tosite=dewiki&totitle=Wasserstoff with an edit token
Yes, that would work. You can also use the wbsetsitelink api, if you prefer (that way you don't need to know about other articles).
Since the purpose is linking articles translated from other wikis, I think their titles and site ids are already known. Aren't they?
Change 214119 had a related patch set uploaded (by Amire80):
WIP: Add a Wikibase link
Change 214119 had a related patch set uploaded (by Amire80):
WIP: Add a Wikibase link
OK, so in https://gerrit.wikimedia.org/r/214119 I tried to do it first with raw API calls, and it didn't work, so I tried it by using PageConnector, as I tried at first, and it still doesn't do the right thing. @hoo, everybody points at you as the PageConnector expert, and it's probably something very simple; can you please take a look? Thanks!
A bit of background: I cheated while developing, because I don't have a local Wikibase installation for testing. To test I copied the function from https://gerrit.wikimedia.org/r/#/c/214119/13/modules/wikibaselink/ext.cx.wikibase.link.js to https://ca.wikipedia.org/wiki/Usuari:Amire80/common.js , and then I translated the article https://ca.wikipedia.org/wiki/Assaf_Amdurski - and it worked, the links were added automatically and without any disruption.
... And this is the Wikidata edit that was done: https://www.wikidata.org/w/index.php?title=Q4808345&diff=prev&oldid=220307587 .
According to this comment, when an existing article is translated into the user namespace, Wikidata links are modified to point to the user namespace. They should not be modified. We should just add links when new articles are created in the main namespace.
I think we already checked this, but a closer look may be needed if it still fails under some circumstances.
This was updated in production yesterday. The comment in ca.wikipedia probably refers to something that happened shortly before the update.
I just tested it carefully:
It definitely doesn't happen anymore. You can see that no link was added to the Wikidata item. Compare it with https://www.wikidata.org/w/index.php?title=Q134396&action=history , where links to test pages were auto-added and manually deleted.
As part of the work on version 2 we asked advanced users to create articles and several reported that wikidata links were not added automatically when publishing (1) (2) (3) (4).
We may want to investigate if there is a regression about this, or in case that it takes too much time for the links to update (e.g., due to Wikidata cache), evaluate what can be done to reduce the confusion.
The issue has been confirmed for version 2, so I created a follow-up ticket to get it fixed: T197221: CX2: Link translated articles with other languages through Wikidata automatically