<?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/7771ec3f58e749599a5bf406debdb101&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/7771ec3f58e749599a5bf406debdb101-098aa25d315cadd0.gif</thumbnail_url><duration>161.173</duration><title>Import Data Layer Schema Matching Overview</title><description>This Loom explains the import data layer changes, focusing on how schema import matching is planned and executed. It describes how schema import functions compare the schema file against the local schema, find existing triples, build schema RIDs, and generate the closest match using case-insensitive normalization. The author notes they abstracted shared functionality for both Superbase import and schema import, using importNodes and importRelations. To verify nothing broke, they tested publish and import in TestVault 2 with a new NodeType new2 and a derivation relationship, confirming the new2 NodeType and imported relation type after import, while noting a bug still needs fixing.</description></oembed>