<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/40d6571412ac4c92b14a6427e058dc9e&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/40d6571412ac4c92b14a6427e058dc9e-a330253fcf7d1f5c.gif</thumbnail_url><duration>156.907</duration><title>Import Roam Graph Nodes into Course Graph</title><description>This Loom demonstrates importing an already published RoamNode from a Roam graph into a CourseDevGraph and verifying that assets like images and links carry over. The author notes that a specific data panel and the image were absent from the pages and attachments, and that to test it they may need to re-broadcast or blast the imported graph registry, which will invalidate things but likely be regenerated on refresh. They then import a discovered share node from the discourse graph into the course dev graph, confirming it appears in assets and was transported locally. They repeat the process in Obsidian for the empty course graph, confirm the import, and check that the image, evidence, and links are present.</description></oembed>