Page MenuHomePhabricator

Automatically connect Abstract Wikipedia articles as a Sitelink in Wikidata, rather than needing the bot / humans to do it
Open, LowPublic

Description

Once we have a place in Wikidata to add an Abstract Wikipedia article as a sitelink (T420420), we should automatically connect the right Abstract Wikipedia article with the right item, and automatically delete it, once deleted.

Given that their titles are always the same in Wikidata and Abstract Wikipedia, it seems not like the best use of contributor work to require a manual connection.

Event Timeline

Jdforrester-WMF renamed this task from Abstract Wikipedia to automatically connect as a Sitelink in Wikidata to Automatically connect Abstract Wikipedia articles as a Sitelink in Wikidata, rather than needing the bot / humans to do it.Mar 25 2026, 5:17 PM
Jdforrester-WMF triaged this task as Low priority.

Just a quick mention that Extension:Cognate does something similar for Wiktionaries, maybe we can retake and adapt it for AW.

I think we need to make a fundamental decision: Do we want to treat the Abstract Wikipedia links as proper sitelinks or somehow special and automated.

As I see it:

regular sitelinkssemi special/automatedspecial/automated
What it meansWe add Abstract Wikipedia as just another wiki and people can add, edit and remove sitelinks as they do for all other wikisWe automatically connect an Abstract Wikipedia article on creation to its respective Item and then everything else works as usual incl. automatic removal of the sitelink if the article is deletedWe fully automatically handle Abstract Wikipedia sitelinks. They are not materialized in the data and therefore not edited but generated as needed.
Advantagesno special treatment; no additional work needed to make it workfairly predictable behavior and only the adding of the initial sitelink would need to be addedno additional edits and maintenance; no mismatch between Item ID and article ID possible
Disadvantagescan lead to mismatch between Item ID and article ID; additional edits and maintenancecan lead to mismatch between Item ID and article ID; additional edits and maintenancepotentially considerable additional work; complexity caused by these sitelinks being special for opaque reasons

I am leaning towards the "semi special/automated" option and I think all that'd be needed is some code on the Wikifunctions side to set the sitelink on article creation. Thoughts?

Additional complication for the "special/automated" option: We have pages on Abstract Wikipedia that should be sitelinked but that are not articles, like help pages, community portal etc. It's probably not great to treat some one way and others another way. (We do that with Wiktionary but I feel this case would be worse because they'd still need to show up in the Item unlink Wiktionary main namespace pages.)

I think we need to make a fundamental decision: Do we want to treat the Abstract Wikipedia links as proper sitelinks or somehow special and automated.

[Snip]

I am leaning towards the "semi special/automated" option and I think all that'd be needed is some code on the Wikifunctions side to set the sitelink on article creation. Thoughts?

Agreed, I think the semi-special model would be most flexible.

It's probably not great to treat some one way and others another way.

I think this is fine. Most of abstract.wp will be made up of the main namespace and the rest can be added manually.

I think we need to make a fundamental decision: Do we want to treat the Abstract Wikipedia links as proper sitelinks or somehow special and automated.

As I see it:

regular sitelinkssemi special/automatedspecial/automated
What it meansWe add Abstract Wikipedia as just another wiki and people can add, edit and remove sitelinks as they do for all other wikisWe automatically connect an Abstract Wikipedia article on creation to its respective Item and then everything else works as usual incl. automatic removal of the sitelink if the article is deletedWe fully automatically handle Abstract Wikipedia sitelinks. They are not materialized in the data and therefore not edited but generated as needed.
Advantagesno special treatment; no additional work needed to make it workfairly predictable behavior and only the adding of the initial sitelink would need to be addedno additional edits and maintenance; no mismatch between Item ID and article ID possible
Disadvantagescan lead to mismatch between Item ID and article ID; additional edits and maintenancecan lead to mismatch between Item ID and article ID; additional edits and maintenancepotentially considerable additional work; complexity caused by these sitelinks being special for opaque reasons

I am leaning towards the "semi special/automated" option and I think all that'd be needed is some code on the Wikifunctions side to set the sitelink on article creation. Thoughts?

Personally, I think that the Wikidata UI should have a button that links to the abstract article. A sitelink isn't truly necessary, because nobody needs to "find" where it is, Q67 on Wikidata is Q67 on Abstract Wikipedia. This also allows users to look on Wikidata and see a button that allows them to create an abstract article that has yet to be created. Unless I'm mistaken, I don't think there's any reason that we need a standard sitelink.

Note we need to consider what to do if a Wikidata item is merged and redirected to another.

I agree that semi-special is a good way forward. Another advantage over full auto is that it can be queried in SPARQL, so analysis will be easier.

One question for the future that nobody has mentioned yet: how should sitelinks look when languages "enable" an AW article to show up in their language-Wikipedia? Would that design impact on this decision?

One question for the future that nobody has mentioned yet: how should sitelinks look when languages "enable" an AW article to show up in their language-Wikipedia? Would that design impact on this decision?

When you say "look like", there are several dimensions here.

Say that I'm a sysop on aawiki and I've enabled an AW article for Q42. Browsing to [[aa:Q42]] will show the abstract article (with explanations that it's from AW). Browsing to e.g. [[ak:Douglas Adams]] will show a link the AW article on AW in the "Tools" menu/section, as part of the "In other projects" section.

(example languages picked as they're shut, so I'm not talking about an active community)

Possible options for site links:

  • It doesn't shows up on Wikidata on [[d:Q42]] at all
  • It shows up on Wikidata as a normal "article" for aa under its local label on [[d:Q42]]
  • It shows up on Wikidata as a special section on [[d:Q42]] for abstract articles
  • It doesn't shows up in the ULS language list on e.g. [[en:Douglas Adams]] at all
  • It shows up in the ULS language list on e.g. [[ak:Douglas Adams]] as a normal "article"
  • It shows up in the ULS language list on e.g. [[ak:Douglas Adams]] as a normal "article" but with a special icon
  • It shows up in the ULS language list on e.g. [[ak:Douglas Adams]] in a special section

… etc.

Stepping back, what happens to abstract.wikipedia.com links in the AW content, when delivered to the language edition?

The reader’s natural expectation would be that following a link in the concrete content would take you to the language-edition article. I don’t think we can formalise that in the AW call that creates the hyperlink, without breaking the navigation within AW, however. I think we would need an article-level “project” parameter corresponding to :abstract: within AW ("https://abstract.wikipedia.org/wiki/Q…") and the relevant project (by “language”) otherwise ("https://aa.wikipedia.org/wiki/{from Z6039K4 for Q…}"). Presumably, where there is no such sitelink for the project, the result would be a hyperlink to the project page that would display the concrete realisation of the AW content for the current content language.

I doubt that enwiki is a singular exception, but there, at least, the content language variant is typically either en-US or en-GB, and it is not clear how an article in American English would be linked to an enwiki article for the en “wiki” project, unless we formally separate the content language (variant) from the project “language”, at least in AW.

One question for the future that nobody has mentioned yet: how should sitelinks look when languages "enable" an AW article to show up in their language-Wikipedia? Would that design impact on this decision?

When you say "look like", there are several dimensions here.

Say that I'm a sysop on aawiki and I've enabled an AW article for Q42. Browsing to [[aa:Q42]] will show the abstract article (with explanations that it's from AW). Browsing to e.g. [[ak:Douglas Adams]] will show a link the AW article on AW in the "Tools" menu/section, as part of the "In other projects" section.

(example languages picked as they're shut, so I'm not talking about an active community)

Possible options for site links:

  • It doesn't shows up on Wikidata on [[d:Q42]] at all
  • It shows up on Wikidata as a normal "article" for aa under its local label on [[d:Q42]]
  • It shows up on Wikidata as a special section on [[d:Q42]] for abstract articles
  • It doesn't shows up in the ULS language list on e.g. [[en:Douglas Adams]] at all
  • It shows up in the ULS language list on e.g. [[ak:Douglas Adams]] as a normal "article"
  • It shows up in the ULS language list on e.g. [[ak:Douglas Adams]] as a normal "article" but with a special icon
  • It shows up in the ULS language list on e.g. [[ak:Douglas Adams]] in a special section

… etc.

I think I favour: It shows up in the ULS language list on e.g. [[ak:Douglas Adams]] as a normal "article" but with a special icon

Per https://meta.wikimedia.org/wiki/Requests_for_comment/The_future_of_Abstract_Wikipedia I believe we are not ready to show links to Abstract Wikipedia articles in other Wikimedia projects yet. The link should for now be unidirectional.