daniel added projects: GeoData, MobileFrontend, PageImages, Wikidata-Page-Banner.daniel updated the task description. (Show Details)
CHANGES TO TASK DESCRIPTION...Show changes to wikidata descriptions associated with pages in `recentchanges` (RC injection), like we do for other changes on wikidata that affect the page. We would also like this kind of "usage" to be visible on a`Action=infoInfo`, like other wikidata usages are - though is is far less critical than the RC injection. ...Similarly, we presently assume that when some information that is "used" on a page changes, that page needs to be re-rendered, in addition to mentioning the change in `recentchanges`, and purging the respective page from CDN. With information that is pulled in by skin layer code, not during parsing, re-rendering is not necessary, but RC injection and CDN purge is still needed# using a materialized usage in in the `wbc_entity_usage` table, and put the description (or other derived information) into the `page_props` table. This would be done via some hook that was triggered while (or after) parsing page content. `MobileFrontend` would then thake the description from `page_props`. We already do something similar with `displaytitle` and `page_image`. This would trigger a re-rendering of the page even when only the page properties need to be updated. To avoid this, we'd need to be able to distinguish between proper in-content usage, and usage only fro page_props. This would probably require a schema change to `wbc_entity_usage`.
# using the notion of "virtual" usage, with a hook in `AffectedPagesFinder` that extensions can use to indicate that they consider the description of a given item "affecting" some page, even though that relationship is not in the database. Allowing extensions to specify whether they want to trigger (or avoid) a re-parse would still require some refactoring, but no schema change. However, virtual usages would not work seamlessly, additional hooks would be needed for the appropriate integration with a`Action_infoInfo` and `Special:EntityUsage`. Maintaining //subscription// would however not be an issue, as long as the virtual usage is of an asepctaspect of the "connected" item of a page - the wiki will be subscribed to these anyway* Wikidata Page Banner (propertystatement)
* In Other Projects Sidebar (sitelinks)
* MobileFrontend (descriptions)
* PageImages (statement)
* Mobile (descriptions* GeoData (statement)TASK DETAILhttps://phabricator.wikimedia.org/T173144EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: danielCc: daniel, thiemowmde, matej_suchanek, hoo, PokestarFan, Halfak, Aklapper, RP88, eranroz, Doc_James, mojoaxel, GoranSMilovanovic, Antohabio, QZanden, Winter, Wikidata-bugs, aude, Lydia_Pintscher, MaxSem, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
