Page MenuHomePhabricator

Add an option to show references for statement returned by property parser function
Open, Needs TriagePublic

Description

Add an option to show the references used by a specific statement returned by the property parser function. I'm not sure if the reference should be wrapped in ref-tags or not, we probably need both versions, and if the references should be wrapped in a template. It will perhaps be to difficult for a first implementation to wrap it in a template, but then we will get the discussion about how to format the reference.

I would prefer that the parser function just pops the option from the arguments as necessary and continue prosessing of the remaining arguments, that is the option is unnamed and can take any position.

Example

{{#property:P123|withref|Q456}}

Event Timeline

jeblad raised the priority of this task from to Needs Triage.
jeblad updated the task description. (Show Details)
jeblad subscribed.
Restricted Application added a subscriber: Aklapper. · View Herald Transcript

This feature request is added after we started to use an infobox with the property parser function in a couple of thousand articles in nowiki. We then started to notice inclusion of properties where it was not clear why it diverged from the text itself. We needed an easy accessible reference for the content imported by the property parser function.

jeblad set Security to None.

If we decide to do this, it should either be per default or via a very simple parameter without any additional arguments (like ids to filter by). The parser function is for very simple, direct data access.

I think this should be declined for the same reasoning as qualifiers being declined (or tending toward declined). I'd wonder a) how to display a full reference (or multiple!) and b) that some (or perhaps most) references are added to properties needing them also use or require qualifiers.

Note that this is after a discussion where the outcome was more or less to require references. No references means all access must be through Lua scripts.

jeblad changed the task status from Open to Stalled.Feb 7 2018, 2:53 PM
Aklapper changed the task status from Stalled to Open.May 12 2020, 9:52 PM

The previous comments don't explain what/who exactly this task is stalled on ("If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on"). Hence resetting task status.