Search result: make associations first-class objects
Remember: as soon as the assoc filter is set (see #402 (closed)), the search result is actually a list of assocs (instead a list of topics).
However, currently the Webclient "emulates" an assoc search result as a list of (player) topics. This is problematic for various reasons (not discussed here).
Example of the status quo: a search result of 2 assocs is actually (partly redundant) presented as 4 (player) topics:
This ticket describes how assocs in a search result could be visualized as first-class objects, that is having explicit "topic lists" and "assoc lists". Yet the aim is an visualization and interaction approach, that is consistent with current Webclient principles.
"Result" label with number of assocs
- e.g. "Result: 2 Associations" (instead "Result: 4 Topics" as it is at the moment)
Don't list assocs twice
- If assoc A<->B is shown don't show it again as B<->A
Visualize an assoc with all of its parts
- assoc type (possibly with its specific color)
- assoc value (visualized already)
- both player topics
- role types
Visualize matching topic players
- Note: if both are set, the topic filter and the assoc filter, the visualized topic players might or might not match the topic filter (because an assoc is always visualized with its both topic players). In this case the user wants to know whether the displayed topic players match the topic filter, or not.
Visualize "revealed-in-topicmap" indicators (analogue to the existing dark blue vertical topic bars). The user wants to know which objects are revealed on the current topicmap already:
- for player topic 1
- for player topic 2
- for the assoc itself
Interaction: from a result assoc the user can
- reveal player topic 1 and select it
- reveal player topic 1 w/o selection
- reveal player topic 2 and select it
- reveal player topic 2 w/o selection
- reveal assoc (along with player topics) and select it
- reveal assoc (along with player topics) w/o selection
By this approach both, visualization and interaction is fully consistent between both, topic results and assoc results. Now we have a fully orthogonal visualization and interaction principle for search results in general, which is consistent with existing Webclient concepts.
This is a follow-up of #402 (closed)
Related: dmx-intern/sprint-planning#236, dmx-intern/sprint-planning#237