{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/eb8d0f513e0148bda7ee6bef730735cc\" frameborder=\"0\" width=\"1670\" height=\"1252\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1252,"width":1670,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1252,"thumbnail_width":1670,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/eb8d0f513e0148bda7ee6bef730735cc-0d577fd1eeb73af0.gif","duration":167.915,"title":"Testing .dg.metadata Stabilizer ID Imports ✅","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."}