Org-roam-graph with org-roam V2

[midas]

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!

@nobiot

(limitation) Export does not seem to be able to resolve my IDs – and fails to export. I do not know exactly why this is the case – I do not use export, so no issue for me. But this affects Org-roam-server’s preview feature (not the graph rendering itself, which is working for me beautifully)

@jethro

@agibragimov

How would the re-design affect org-roam-server? Does it mean that the links to headlines would also be displayed in the graph?

Queries will need to be rewritten to match the new schema. Links to headlines WITH IDS (nodes) can be displayed in the graph.

@jethro

Basically everything else will break: org-roam-bibtex, org-roam-server included.

@jethro

@midas

Does this mean that each node/subtree-with-ID will appear as its own node in graph (via org-roam-server)? That would be fantastic!

Yes, but org-roam-server needs to be updated for the new db schema.

[jethro]

@midas

I wonder if early-adopters can comment on their experiences with org-roam-server and graphing on V2.

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.

[midas]

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

[scotto]

@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, File1.org:

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

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

and File2.org:

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

* h2.1
  :PROPERTIES:
  :ID:       20210702T193026.992153
  :END:
  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?