This can also create new insights and it would be nice if there are both options. Furthermore it helps working with huge amounts of files if you are working with the principle of atomicy. Adjustible forces like in Obsidian might help to handle the chaotic nature of Luhmann-like Zettelkasten likewise. Also it can help to reduce graph view and to get a better overwiew about a specific topic or problem. Limiting the graph to one or more folders might be useful for those who are working with a bunch of folders to avoid a mess and keeping Zettelkasten accessible.
Possibility to choose folders and adjust forces
Zettlr graph archive#
Niklas Luhmann Archive shows that visualization of Folgezettel is basicly possible.Ĥ. But it might be possible that some people out there using it. Personally I dropped that technique and I am using Structure Zettels because it's easier to store Zettels in various lines of reasoning inside structure zettels. That could be helpful for people working like Niklas Luhmann. On top of that I see no need for scrolling upwarts and downwarts, if you are able to simply zoom in and out the parts of the graph you are interested in. I think zooming in and out with scroll wheel feels more natural. I think this depends on your point of view. Using scroll wheel for zooming in and out Maybe it's also possible to get filename from YAML-header.Ģ. I think it would be really helpful to have a switch for the name which is displayed in the graph view, so you are able to switch from file name to first header and vice versa. So here are some of my ideas for possible features of the graph view: Works even great under immense time constrains! I really like to work with Zettlr for more than one and a half years and I also used it for my first state examination for teaching geography and social studies. The graph building process still takes a lot of time, depending on how many links you have, there is lots of room for optimization.īeta Was this translation helpful? Give feedback.Īt first I would like to thank you for your work.Links overlap each other and in general the simulation is somewhat awkward (I couldn't find any solutions for this yet).Currently the graph will rebuild itself even if nothing in the link structure has changed (i.e.Dragging the network graph does not yet work.Clicking on a vertex should highlight the path from its parent to all leaf nodesĪlso, there are a few known issues that I will be gradually improving, so again: Please do not open an issue for these as well!.Possibly integrate a better layouting mechanism such as Fruchterman-Reingold or MDS-based layouts (e.g., Kamada/Kawai).Different color shading of the links between nodes based on them being either asymmetrical or mutual ( MAN criterion).Weighing of edges, for example utilizing edge betweenness centrality.Implement HITS (Hubs/Authority detection algorithm).Currently the community detection uses the weak criterion for clustering components I plan to also add the strong community detection criterion (which will identify different components even if they are connected, if there is one link which is asymmetrical, and not mutual).Add arrow heads to the links between nodes to visualize the directionality of the arcs.Highlight specific nodes without completely hiding the others.Center the view on specific nodes (implemented).
Filter nodes by path/folder/title/tags (implemented with path, not yet tags).Allow vertices to be scaled according to various node centrality measures (eigenvector centrality, betweenness centrality, degree centrality).
I'll also consult faculty at my institute to make the graph view scientifically correct. I am planning on playing around with a lot of different ways of analyzing and visualizing networks since I have to do that for my PhD as well. There are a few features I already have planned, please refrain from opening issues for these. Please utilize the tree-like structure of comments in this thread to try to keep it a little bit ordered :) Already Planned This is meant to prevent the issue tracker from flooding with numerous different feature requests. So one word of caution: If you would like to have a feature for the graph view, please discuss it here and DO NOT OPEN AN ISSUE for this.
That being said: In the future I plan on adding more features depending on what works, and what doesn't. As I made clear in the changelog, the current implementation is still in its infancy. Today, Zettlr 2.2.2 shipped with the new graph view.
0 kommentar(er)
