<?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/eb8d0f513e0148bda7ee6bef730735cc&quot; frameborder=&quot;0&quot; width=&quot;1670&quot; height=&quot;1252&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1252</height><width>1670</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1252</thumbnail_height><thumbnail_width>1670</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/eb8d0f513e0148bda7ee6bef730735cc-0d577fd1eeb73af0.gif</thumbnail_url><duration>167.915</duration><title>Testing .dg.metadata Stabilizer ID Imports ✅</title><description>I’m testing how the Digimeta data performs as the stabilizer ID for importing. I imported new nodes from this vault and confirmed the dg.metadata file is created correctly, with the space URI and space name matching what’s in the DB. Next, I modified the folder name, deleted the file, reimported, and verified it goes into the changed folder and updates the metadata. Finally, I renamed the space in the DB, reimported, and confirmed the space name in dg.metadata updates correctly while staying in the right local folder. No action is requested from viewers.</description></oembed>