Template allowing to output trees from Wikidata content. Based on Module:Tree.
||required or optional?
||The numeric identifier of the property to base the tree on ie the XX part in PXX.
||The base item(s) identifiers use to start the tree. List of QXX identifiers separated by spaces.
||Maximum height of the tree
||Language code in which the labels will be found
The template is intended to be used in the following namespaces:
no namespace specified
The template is intended to be used by the following user groups:
no user group specified
Tack with bowl to the right
The tack symbol with a bowl to the right "⊸" means "end of the branch". There are no further child items for that branch.
Small three dots
Small three dots "…" means "child item abbreviated". There is further child item for that branch, but it is abbreviated because it already exceeded the recursion limit. If you want to show abbreviated items, increase the recursion number setting.
Infinity symbol and Upwards arrow
Infinity symbol and upwards arrow "∞ ↑" means infinite loop is detected (i.e. a child branch is in fact linking back to one of its own ancesters previously listed in the tree). The same item is linked with one or more symbols between parentheses (like at sign "@", asterisk "*", or sharp "#").
One or more symbols between parenthses (like at sign "@", asterisk "*", or sharp "#") are used when same item appears twice or more times in different branches of the tree. Same items are abbreviated by these symbols except the last occurrence.
Huge tree sometimes exceeds the limit of "expensive parser function count" (w:en:WP:EXPENSIVE). As of 2017, maximum expensive parser function count is 500. When accessing one Wikidata item page through Lua function (for example mw.wikibase.getEntity()), it raises expensive parser function count by one. So it is not possible to render huge tree which includes over 500 items. If the count reaches over 500, this template returns error
Lua error: too many expensive function calls.
And automatically categorized into Category:Pages with too many expensive parser function calls. In such case, try decreasing recursion number setting for shortening tree.
You can check the current expensive parser function count of each page by following manner.
Go to "Edit" mode → "Show preview" → Scroll down to around the middle of the preview page → Click and open the "Parser profiling data:" table → Check Expensive parser function count shown there, like
142/500. These statistics reports can also found without using edit preview on any page, by looking for the HTML code at end of the main content of the generated page, where they are represented as HTML comments.