<?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/44cdf4b1ec93428fb3c32cc591b0b057&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/44cdf4b1ec93428fb3c32cc591b0b057-671f5a7cf6b40930.gif</thumbnail_url><duration>69.815</duration><title>Checking Legacy Asset Import in New Space</title><description>This Loom tests whether importing a legacy asset using an outsource path works correctly with a new import mechanism into another space. The speaker takes a node that already has a small asset, performs the import, and confirms the asset is now present in the target space. After importing, they check the result and note that the asset has not yet been fully reflected as expected. The main focus is validating the import behavior across spaces under the new mechanism.</description></oembed>