As far as I can see, when you export a Roam graph in Markdown format, links to blocks are not preserved. Links to pages show up as [[name]] and are imported correctly but references to blocks don’t show up in any way. It would seem that block-level links/references are not preserved in any way when exporting to Markdown.
So - I assume in theory it’s possible to import an EDN file into Obsidian in a way that preserves block-level links. Just wondering if anyone knows of a tool to do this?
I assume that Roam has no public documentation for its EDN format.
They’re explicitly admittedly that their earlier markdown and json exports were only partial. Which isn’t good news for anyone who has paid to lock a lot of their data into Roam. They’re also suggesting that they couldn’t find a way to export the total data into json (that surprised me a bit, but I’m not an expert); markdown I understand because it doesn’t have any native way of dealing with blocks. Or backlinks.
I’m sure that someone who understood the EDN format could produce a better set of Obsidian compatible markdown files, but there might still be some features that don’t align.
The EDN format seems understandable if you open it up in a text editor, although very cumbersome.
The JSON format preserves enough for my liking - it does preserve the block references (I tried importing it into Logseq) but it does not keep the back-links from a referenced block, which I can live without. Is there a way to import the JSON into Obsidian?
Edit: the above is incorrect - the JSON does seem to keep back-links from a referenced block when it’s imported into, for example, Logseq. That is, the github issue I linked above does not apply when the JSON is imported into a non-Roam service.
I amended my post above: when I import the JSON into Logseq, it also preserves the count of back-links from a referenced block. So the github issue above is not reproduced when importing the JSON into a non-Roam service, which means the JSON should have all the info needed?
The current importer works from the markdown, but the markdown as exported from Roam doesn’t include any details about block links. Therefore it would be impossible to write a markdown importer that keeps this info, any importer would have to deal with the JSON (or the EDN).
@BigHead my suggestion would be to add a request in #plugins giving as much information as you can about the EDN format (maybe an example would be nice or where to get a sample file). Perhaps another ex-roam user (or someone who uses both roam and obsidian) can help out, but if not another plugin developer might need all that info before they consider volunteering their time.
I just stumbled across this post. I wrote a Roam JSON to Obsidian converter that preserves block references (inserts ^blockids and links to them). It’s available here: https://github.com/renerocksai/rj2obs
It’s not very polished yet but it did the job of making my Roam JSON export usable in Obsidian, especially when followed by Obsidian’s Markdown importer cleanup.
There hasn’t been any activity for 5 days, could you please see if you’d like to pick any of the existing answers as the solution, or do you still need help with something?
Would appreciate it if you could clarify on that, thanks!
Thank you for creating this. I’m not a coder but I’d like to try to use this. I now have Python installed on my Windows PC but can’t figure out how to get this to run from the command line. I’m used to pasting JS code blocks into Roam but don’t understand how to make this function. I’m new to Obsidian as well - does the code run in Obsidian or does your Python code prompt for an input/upload of the Roam JSON export?
Thank you @renerocksai for creating this script for us!
I got an error and posted an issue for you on Github. It looks like Anwesh has submitted a pull request that will fix the error and make other improvements. Can you take a look?
