{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/93c233a0522c4542a159230a80f3e3a1\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/93c233a0522c4542a159230a80f3e3a1-b59acd18ea99b753.gif","duration":94.242,"title":"Matching Relations Across Import Graphs","description":"This Loom discusses extracting and reusing shared code for matching a relation to an existing triple during graph imports. The author removed a function from the Roam import because the Roam import was a large PR, but later found the same code needed in the Obsidian PR and other places. They reference PR guidelines to isolate common code in the PR and then explain the logic for aligning Roam-sourced relations to destination graph triples. The process can match by existing ID when already imported and otherwise looks for name, including a special case for Roam default types."}