This may happen after the usage aspect C is deployed. It will require some more thinking, though, since the option formatterUrlProperty is only available to the repository.
Description
Description
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Resolved | Lydia_Pintscher | T49288 [Epic] Track Wikidata entity usage on client pages | ||
| Open | None | T175376 Parser and Lua functions should track changes to 'formatter URL' property | ||
| Resolved | hoo | T151717 Usage tracking: record which statement group is used | ||
| · · · |
Event Timeline
Comment Actions
@matej_suchanek , this is good point. I think it is not related to usage aspect C directly. Can you please elaborate ?
Currently either someone access it explicitly (getEntity(P214)) or implicitly using formatValue and similar stuff. I think it is/should be handled in UsageTrackingSnakFormatter.
PS: C is going to be evaluated soon in https://gerrit.wikimedia.org/r/#/c/375544/ (if this could have any negative impact please -1 there)
Comment Actions
Now this is not being tracked at all and we are not able to focus a single property. So the only way is to use an inaccurate aspect (O/X) that tracks all changes to the property, which are irrelevant to individual articles. With C introduction, the aspect will be as simple as C.P1630.