Allow recursivity (making depictions of "band" show depictions of "rock band")

[nicolas-raoul]

Let's say a visitor wants to see depictions of bands. The visitor might find it strange to see zero rock band.

The depictions page for band does not show the depictions for rock band.

It would be great to have a checkbox "Include subclasses and instances".

Thanks! :-)

[stevenliuyi]

Thank you for the suggestion. It's definitely a very useful feature, but as far as I know it seems the query is not that straight forward?

So for items that have tons of subclasses and/or instances, it may require sending many API requests at the same time, which would exceed the rate limit.

I'm not sure if there is a way to achieve this in one query. It would be great if we are able to incorporate the structured data on Commons in WDQS in some way.

[nicolas-raoul]

I created the issue because it would be a very useful feature. You are right, it is not straightforward. Creating this feature will probably require modifying Wikidata server-side, for instance by improving caching vastly, and maybe even by creating new APIs.

The required server-side capabilities do not exist yet, because your tool is the first to cater to this new need. Being a pioneer means you will probably have to create a few Phabricator tickets :-)

• One API method could returns all subclasses of a particular class
• Another could return all instances of a particular class+subclasses
• Another could return all Commons depictions of a particular class+subclasses
• Another could return all Commons depictions of all instances of a particular class+subclasses We don't need real-time results: Results in December 2020 will probably be almost the same as results in November 2020. Maybe one monthly calculation + caching + some cache invalidation. If this caching works well, results could be served in a second.