Org-roam-graph with org-roam V2

With exciting developments in org-roam V2, a question on my mind is the state of Graphing with the new version. I wonder if early-adopters can comment on their experiences with org-roam-server and graphing on V2. Your insights into what works, what doesn’t work, what is the basic config necessary to get it to perform, etc. would be most appreciated.

Org-roam-server and graphing has come up on the thread announcing org-roam-V2. That thread has grown very very long. Below are links to a few of the posts that deal with the topic. I am spinning off the topic with the hope that a more focused thread on graphic can spurn some focused feedback/input from early adopters. Thanks!


It really just won’t work yet, until org-roam-server is updated to support the new DB schema. I’m certain that it’ll be simpler though.

It seems org-roam-graph has been updated for V2, and that could mean org-roam-server might soon follow. Encouraging news!

@jethro, did you mean that graphing won’t work, or just that org-roam-server won’t work?

I’m asking because the graphs I see in V2 don’t match my understanding of how the new headline nodes should behave – from the V2 announcement:

… Nodes also have an implicit hierarchical structure, from the levels in the Org file. …

For example, if I have two org-roam files,

:ID:       20210702T192356.306099
#+title: File1

* h1.1
* h1.2
  :ID:       20210702T192737.308439
*** h1.2.1
*** h1.2.2
  :ID:       20210702T192756.464588


:ID:       20210702T192839.233331
#+title: File2

* h2.1
  :ID:       20210702T193026.992153
  link: [[id:20210702T192756.464588][h1.2.2]]
* h2.2

and if I run M-x org-roam-graph, the graph I see is:


But my understanding is that the graph should instead look more like this:

Is V2 graphing just not implemented yet, or does my understanding not match your intentions?

1 Like