smaroukis
commented
5 months ago +1 My use case is when studying a new topic I don't really know the exact hierarchy of information and want to quickly re-arrange the hierarchy as I find new topics that may nested under a previous topic, or I want to re-group existing topics under a new parent -- really it comes down to quickly inserting a node and redefining the edges of the existing nodes to point to/from this new node.
For example I recently had a Hierarchy Note (List note in v4) of:
- [[563 Computer Science]]
- [[Software Fundamentals]]
- [[Algorithms]]
- [[Data Structures]]
- [[Programming Languages]]
- [[C-Programming]]
- [[Artificial Intelligence]]
And I wanted to add a "Search Algorithms" under "Algorithms", the problem being I already had notes with explicitly defined
up::[[Algorithms]] (not shown in the Hirearchy note since the relationship was defined later)
Currently I change the name of [[Algorithms]] to [[Search Algorithms]] which should update all the notes with explicit definitions to up::[[Search Algorithms]], but then I have to make sure that all those notes actually should be children of [[Search Algorithms]] versus [[Algorithms]]
It would be much faster to have a visual and dynamic way of viewing these so I could just reorganize by adding in the [[Search Algorithms]] node and re-connecting the notes with explicit up::, and this action would update the fields in the corresponding note
I'm open to suggestions on current workflows or workarounds!
As the whiteboard feature of Obsidian appears, it is hoped that the plugin can support the canvas data of the whiteboard and use the whiteboard as a display option, and use the custom relationship and description in the plugin configuration as connections and annotations.