Org-roam major redesign

[jethro]

@midas

I love the idea. If I understand it correctly, this means every subtree with an ID will be cached in org-roam db and treated as its own atomic note.

That is correct.

@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.

@midas

I’ve been using org and org-id for 1.5 years and have highly inter-linked subtrees across 4-5 very long org files. It sounds like org-roam v2 will be able to take this structure and generate graphs through org-roam-server.

Issues with processing large org files still remain (for now), but it will support the structure.

@midas

Will this unify roam-tags with regular org-tags?

Yes, Tags will be specified via Org tags (and FILETAGS for file-level nodes)

@midas

How will this affect org-id? I believe org-id currently catalogs the names of org files and the IDs they contain. It is kept in a file ( .something file in .emacs.d , I believe) to serve as a look-up table (I assume).

Unaffected. Org-roam duplicates that information, and can choose not to use it.

@midas

Thanks for building org-roam v2. I look forward to trying it when it is available (is it already?)

I’ve personally been using the V2 branch for a few months now and making changes where necessary. Works fine for the minimal subset of features I rely on.