New view: relationships map

Atlassian had this tool called Compass which had an interesting feature: a dependency map which allowed you to explore a graph by going from node to node.
I think something like this would be a great addition to Fibery.

Dependency map (1)

3 Likes

it“s great!
I have also seen this coming up in other high-level knowledge navigation apps.

the really nice thing about it: it allows for navigating heterogenous pathways, seamlessly connecting different (entity) types!

– … this pretty much relates to the whole aspect of ā€˜complex model spaces’ / ā€˜concept maps’ that is part of this whiteboard discussion, IMO.

:point_right: Whiteboard as context (= information) – how to use this 'insight' in Fibery? - #15 by lerone

Have you tried the experimental feature for showing entity collections?

I haven’t tried it but I saw the video, and it’s a somewhat different use case imo

Please try it and let us know what the missing features are :slight_smile:

It is exactly the same use case as I see it

hey there,

I tested it, and generally the multi-entity insert is a great function, especially given it“s flexibility around filtering etc! :rocket:

From comparing the 2 experiences + my knowledge of similar functions in other tools, I“d say one can go very far with this.
There remains a (closable) gap between the 2 use cases / experiences of building an (explorational) view and navigating, I would think. With navigation – like in the so-named ā€˜Compass’ – being automatic and instant, that is easily navigable. While the current experinmental feature needs clicking and decisioning, and produces a stable view, not a dynamica one, like the Atlassian… :compass:

The OP (@Mircea_Braescu ) would of course have to say whether this was on his / her mind; but that is where I feel the difference currently. :hand_with_index_finger_and_thumb_crossed:

Plus, I deliberately wrote ā€˜(closable) gap’ bec I think there is an easy way to reconcile both modalities (exploration & building view vs. dynamic, instant navigation) and get to a hybrid: if the last toggle, showing the selectable collections, would give a hover preview of all the titles of the entity set, it would potentially change the experience ā€˜dramatically’, in terms of giving that feel of contextual, ad-hoc navigation. :thinking: (It would be even more so, if all the hovers over context menus would open the modals… but that is not a vote for that… :upside_down_face:)

In Fibery there are situations when you have dozens of collections with thousands entities, so no simple solutions will work. What we implemented is the only one we found can work for many collections and many entities. If you can invent a better approach, we’d be happy to hear it

ok, sorry. I canĀ“t contribute more than some constructive ā€˜thinking along’ as a proficient & interested simple user; and the idea of navigation vs. view building (for differentiating use cases). and the proposal / idea I already gave (hover preview). :sunflower:

you have dozens of collections with thousands entities

Yes, but any single entity will usually only be connected to a few other entities, probably not more than a dozen or so, and the benefit with the suggested approach is that it would be a quick and non-overwhelming approach to navigate and visualize what could otherwise be spaghetti (a big graph / network)

1 Like

Actually, in our Fibery setup we use connections heavily. And while the classic 7±2 rule applies, for connections of one type, we have entities connect to many other types.

One example would be a UI Component entity, it’ll connect to:

  1. Child/parent components
  2. Business Object Entity
  3. Screen/Page
  4. Copy Strings and Errors
  5. Features/Actions that they trigger

So together these will amount to a good amount of connections that I may want to see or not. And other key nodes will have similar number of connections.

It’s not an unsurmountable problem and I’ve actually made a PoC in a completely different space that solved that problem, but it’s not trivial. And it’s pretty much in line with what the team has implemented with the ability to unfurl and show/hide edges based on type.

1 Like

Please try it and let us know what the missing features are

I tried it and it’s exactly what it showed in the video. A powerful way to add related entities to an whiteboard, and I’m sure we’ll make use of it in some cases, but it’s not a tool I would to navigate through the graph of relationships.

With a view like the one in compass I can get to a 3rd degree removed dependency in 3 clicks.

The closest approximation of that in Fibery would be the entity details view. I see the related entities for an item and I click one of them… Then I see the details and related entities of that item and click another one … and so on and so forth.