Perhaps we are not just talking about tree/hierarchy in graph, but also a separate on-demand graph feature and/or graph with advanced feature. On demand graph can allow display of only relevant or requested nodes.
- Depending on the objects retrieval mechanism:
– Object inclusion list which resembles a graph for collection, or Whiteboards / canvas
– Object exclusion list which is also Obsidian’s mechanism for both global and local graph - Different node positioning methods serve different note-taking purpose
– Manual/organic positioning, which is also logic behind Ability to Resize a Graph Node and whiteboard, is the best for brainstorming.
– Automatic / Inferred positioning is great for pattern observation, and would work well with a larger amount of objects. One thing that needs to be resolved with using inferred position for tree/hierarchy is what do we do with conflicts of connection logic. For example, if Object A is Core of Object B, but Object B is also Core of Object A, how do we expect graph to display both on top of another? Local graph or more accurately primary object logic could prioritise this connection display.
All of these mechanisms would work well with my different note-taking needs, as static and dynamic connections exist with different contexts.
Another related topic: Object/attribute collection - use hierarchies and semantic versioning