The properties should be kind of sorted.
Therefore, we should have a list of 20-30 important properties that show up first, a blacklist for properties that shouldn't show up and a way to sort the Statements in the placeholder accordingly.
The first statement shown should probably always be "instance of".
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | thiemowmde | T142940 Create client functionality for getting human readable wikitext from Wikibase statements | |||
Declined | None | T99897 {{#property}} parser function should output EntityIdValues as local wiki links, once we have article placeholders | |||
Invalid | Lydia_Pintscher | T99896 Use Lua for custom rendering of entity data on Special:ShowEntity | |||
Resolved | Lucie | T99895 [Epic] Article placeholder based on data from Wikidata | |||
Resolved | Lucie | T109445 [Story] Display the Article Placeholder | |||
Resolved | Lucie | T109447 [Story] default display for article placeholder | |||
Resolved | Lucie | T113936 [Story] initial default display of article placeholder | |||
Duplicate | Lucie | T113952 [Story] Sorting properties | |||
Declined | Lucie | T117556 Limit number of statements | |||
Invalid | Lucie | T117681 [RfC] Ordering of statement groups in ArticlePlaceholder |
Event Timeline
Comment Actions
Change 278726 had a related patch set uploaded (by Lucie Kaffee):
Add a parser for the property page