We’re not sure if oldwikisource is already a Wikibase client at all, and how much work it would take to enable arbitrary access on it. Investigate!
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T109579 [Epic] Give more sister projects access to Wikidata | |||
| Open | None | T360048 [EPIC] Drawbacks of 1 sitelink per Item per wiki implementation | |||
| Stalled | None | T54971 [Goal] Sitelinks and arbitrary accesses to Incubator, OldWikisource and BetaWikiversity | |||
| Resolved | Ladsgroup | T138332 Interwiki links to/from Multilingual Wikisource | |||
| Resolved | Ladsgroup | T202543 Enable arbitrary access on oldwikisource & document the process | |||
| Resolved | Ladsgroup | T204706 Investigation: status of oldwikisource in relation to wikidatawiki |
Event Timeline
Comment Actions
We’re not sure if oldwikisource is already a Wikibase client at all
Not it is not
and how much work it would take to enable arbitrary access on it.
As far as I know it should be no different to turning on arbitrary access for another other project.
I think this task was created for @Ladsgroup to double check and confirm this?
Any chance you can take a look at this has been sat here for some weeks now.
Comment Actions
I spent one hour digging the code and apparently sitelinks stuff and client are different things. The way that sitelinks in repo works is (according to SiteLinkTargetProvider) and then get valid groups + special wikis and then discards everything else. Meaning as long as we are not adding 'sources' to $wgWBClientSettings['specialSiteLinkGroups'] and $wgWBRepoSettings['specialSiteLinkGroups'], we are fine. It's interesting to see 'oldwikisource' is not a 'wikisource' but a 'sources' wiki but if anyone fixes it, it will accidentally enable sitelinks for oldwikisource.
If we want to enable client on sourceswiki, we need to add it to the client dblist and pull it on mwmaint1002, make the tables and then just sync the dblist everywhere. I can do it later.