video1.0<iframe src="https://www.loom.com/embed/ba9e6165469747fa8fc876560c60fc96" frameborder="0" width="1662" height="1246" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12461662Loomhttps://www.loom.com12461662https://cdn.loom.com/sessions/thumbnails/ba9e6165469747fa8fc876560c60fc96-3ad82ad8b39c6ca9.gif381.425This Loom explains how Obsidian distinguishes between file paths and source paths when importing content from Roam/Firebase. It clarifies that the file path reflects how links appear in the original markdown, while the source path is the absolute filename from Firebase metadata. Because Obsidian uses real files, it avoids collisions, but Roam can have multiple Firebase URLs sharing the same metadata filing, requiring collision resolution via stable SHA-based disambiguation. The discussion also covers mapping link paths relative to the vault, disambiguating when markdown may look like a URL, and updating import handling so output includes both FilePath and SourcePath.