Currently, dashboard properties must be listed explicitly in the {{Property dashboard}} template configuration.
p1963 (properties for this type) is a Wikidata property used on items to declare which properties are expected for instances of that type.
It would be useful to allow a dashboard to pull its property list directly from p1963 values on a given item, so that the dashboard stays automatically in sync with the community-maintained list of expected properties for that type, without requiring manual updates to the template configuration.
For example, Q39715 “lighthouse” lists some 18 properties via p1963. inteGraality would use that list to define the 18 columns.
Open questions
how to define which p1963 to use:
I can see two possibilities:
- Explicit configuration. The user explicitly says it wants the p1963 of Q39715.
- Auto-discovery: inteGraality sniffs the p31 of the selected items
- Difficulty: what if the item selected has more than one p31?
- Difficulty: what if the desired type is not done through p31? (Property page gives the example of Q901 “scientist” which goes into “occupation”)
Transitivity
Items could have p1963 values inherited through the type hierarchy (p279 subclass) − should inteGraality try to resolve that or not?
Exclusive vs hybrid
Does p1963 take over the dashboard, or do we want to allow mixing classic configuration together with the columns taken from p1963?
Stability
the dashboard would change between runs if edits are made to p1963 − is that a problem, might be surprising to users?
(Also, do we need to take that into account for Redis caching invalidation?)
Genericity
The request is about using p1963 support ; but it’s really about sourcing columns based on the values of a particular property set on a particular item − should we already allow using any property? That would condition the syntax to use.
Ordering
How to decide on the column order? It must be stable to avoid dashboard dirty diff.
- just take the order of properties listed in p1963 (users may use scripts like ReorderValues)
- (alternatively, reorder by alpha order?)
Minor points
- If Explicit configuration − which syntax to use?
- dedicated template parameter, | properties_from_type = Q5
- special value in the properties field, maybe something like | properties = @Q5 or | properties = P1963(Q5)
Tentative conclusion
- Use explicit configuration
- No transitivity support
- support for hybrid dashboards
- do not limit to p1963 (we might want to have an allowlist still?)
- preserve the on-wiki order of p1963
that would leads to the syntax | properties = P1963(Q5)