<?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/b5dc1662b79e4b56a7ff0e3bf74b7039&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/b5dc1662b79e4b56a7ff0e3bf74b7039-582abc65412d7d6c.gif</thumbnail_url><duration>470.81</duration><title>Importing and Managing Node Types in Discourse Graphs</title><description>In this video, I walk through the process of importing nodes and updating our data structure in the main branch and a new branch. I also address some issues with the URI parsing and the importance of handling node types correctly, particularly with the Test2Node type. After some troubleshooting, I successfully acquired the Test2Node type and ensured it has the proper schema and provenance info. I highlight the need for further improvements in the import code to enhance efficiency. Please review the changes and let me know if you encounter any issues.</description></oembed>