Template talk:Wikidata link

Hiding links
I'm not sure I agree with hiding these links by removing the colour. It seems unlikely that they'll ever be used if they can't be seen! I understand that there's a discussion going on about annotations and the nature of links, but it seems to me that this template is specifically for works where editors want to make interwiki links (but don't want to have to come back an update them as e.g. Wikipedia articles get written or whatever). Do you mind if we revert to showing the colour? — Sam Wilson 01:58, 8 March 2021 (UTC)
 * The ability to turn the links on and off in a sidebar sounds fun; and just have them on by default; and have them off for print versions. — billinghurst  sDrewth  03:34, 8 March 2021 (UTC)

Force link to another wikisource's item?
Can, or could, we utilise this template to point to an edition of a work at another Wikisource? In a way similar to how it links to an enWP item. I would like to provide a direct link to a work at zhWS, for linking on a disambig page, though that isn't possible with the current setup. If it is not automatic, it would be useful if we were able to utilise parameters like to do so. — billinghurst  sDrewth  03:23, 11 January 2023 (UTC)


 * Yes, that sounds like a good idea. I wonder if the addition of just one parameter would be simpler though, e.g.  because I'm not sure when it'd make sense to require a link to a specific project but then not care what language it's in. Also, would there be times when you want it to use the label of the destination (e.g.  in this case)? Sam Wilson 04:14, 11 January 2023 (UTC)
 * My only concern about one long parameter is that we will need to provide an ever growing list, as I am not trusting of a universal knowledge of those, not that two parameters is easier. What about with first rendition of update we just provide a language and to say that we are forcing a link to a Wikisource (only) as they are the primary aim outside of enWP. Remember that we are typically putting links to editions primarily (single language at a single wiki), though maybe maybe maybe a versions page, though that will be less likely. — billinghurst  sDrewth  05:18, 11 January 2023 (UTC)
 * language of destination? dunno, don't we already allow for text override? Question is are we taking the work name, or are we taking the description of the item. — billinghurst  sDrewth  05:19, 11 January 2023 (UTC)
 * @Samwilson: The problem you will run into is maintaining a mapping of interwiki/interlanguage prefixes to database/sitelink site ids (or vice versa). I recommend you switch away from using distinct interwiki/interlanguage prefixes and instead always link through Wikidata which solves this problem for you with d:Special:GoToLinkedPage, e.g., d:Special:GoToLinkedPage/zhwikisource/Q18858287. Of course there is still the issue of how you want to decide which site id you want to use (grouped by project and language, etc.) and of course how you decide upon the link label. Once you start going down this path you will run into lots of messiness though, e.g., Special language codes. FYI: this template and module are substantially similar to label and or, e.g.,   &rarr;  (notice how it found the Chinese). I always thought it would be nice if mw:Extension:SiteMatrix had a Scribunto Lua interface. —Uzume (talk) 05:14, 22 April 2024 (UTC)
 * I'm not sure I understand: do you mean the fact that links made by this template use  or   interwiki links? That works fine, for the current design I think. The feature request here is to make it possible to link to another Wikisource project, and you're right the similarity between this and label perhaps make it more useful to use that template for the cross-Wikisource linking task. Because the whole point of this template is that you don't need to know what project the link is going to point to — because the best one will hopefully change in the future (i.e. for now we link to Reasonator but at some point there will be an English Wikipedia article that'll be more appropriate). If we want to be able to link to a Wikisource in a specific language, then we already know where we want the link to go, we just don't know the specific page name. Sorry if I'm misunderstanding things! Sam Wilson 05:41, 22 April 2024 (UTC)
 * @Samwilson: Right, there is some fixed priority and a fallback chain. I get it. My point was with all the projects and languages the fallback chain can get very long and complex. When such is simple and small using direct interwiki linking can be fine but when you want to allow all or most of WMF as part of the fallback chain it gets complex and hard and I was just suggesting some methods forward towards that end. I do not think it makes much sense to add support for zhwikisource without adding support for all the other wikisource languages. —Uzume (talk) 06:09, 22 April 2024 (UTC)