Page MenuHomePhabricator

FileAnnotations prototype: Search: In the universal search, collapse the same concepts together
Closed, DeclinedPublic

Description

Concepts and their multiple projections. Being able to search across all different results seems great. I'm wondering whether items that are the exact same concept (Maria of Austria in wikipedia and Wikidata) could/should be bundled in some way. Keeping the list flat has some advantages, but we may want to consider how many results users may often find that seem just a repetition of each other; and more importantly whether users get confused on which one they really want to pick.

Event Timeline

You mean something like this, right?

UncollapsedCollapsed
uncollapsed.png (333×533 px, 111 KB)
collapsed.png (253×533 px, 57 KB)

Lets come back to this after T154893: FileAnnotations: Review information in wikidata annotations, search results and annotation cards. We might choose to hide those results completely.

You mean something like this, right?

Yes, that is a possible execution. It can be even more compact by not repeating the title for the elements that are projections of the same topic on a different project. That is, showing the main concept and the different ways in which it is represented, "Mariana of Austria" (data, article, image category).
The specific painting "Diego Velázquez 032.jpg" is a different element and may not be compacted as part of Mariana of Austria.

The specific painting "Diego Velázquez 032.jpg" is a different element and may not be compacted as part of Mariana of Austria.

That is the tricky part. I left the names in because sometimes the user cant be sure if that is what they want. These 'related/collapsed' items are coming from the Mariana of Austria Wikidata item, and thus are the canonical image, or category etc.

Ramsey-WMF subscribed.

Since the 2016/2017 FileAnnotations prototype work is now quite outdated and both Wikidata and Commons have new features and design plans (like moving new features to Vue.js on Commons), and the extension is not actively under development, the best thing to do is close these tasks and create new ones when/if there's a team available to pick up development on this feature.