I have been searching for a method to display references to notes across different vaults, such as using ![[.......md]]. However, I found that this method does not directly display notes from another vault, and if you click to open them, they are not opened by Obsidian. Recently, I discovered that it seems possible to use mklink /j to achieve this functionality.
Simply put, you can create a shortcut in the vault where you want to reference another vault. For example, let’s call the vault being referenced “vault B” and the vault referencing it “vault A”. My synchronization environment is OneDrive + Git + Remotely Save, and both vaults are configured this way. After entering the command in CMD, I found that vault A in OneDrive would upload the contents of vault B, and Git would also upload these files (not just a simple shortcut). However, it is currently working well, especially when combined with Custom Attachment Location.
I have done the following tests. I opened vault A and vault B with Obsidian and edited them simultaneously. I found that they both work well, allowing input of content and insertion of images. Git synchronization also works without any issues. In the OneDrive web version, Vault B in Vault A is no longer a shortcut but a complete folder. (I use OneDrive for Business for Vault A and OneDrive Personal for Vault B). I feel that through this method, we can effectively reference content from other vaults (although it will take up space again, they maintain the same synchronization between them)
Thank you both for your replies. I tried using Obsidian URI, but it seems it cannot achieve the functionality similar to ![]. Additionally, I found that neither method can effectively handle situations where there are attachments in the file.
The only issue I have discovered so far is that if it is a canvas file, the images in the canvas file cannot be displayed correctly because it does not use the shortest path.
I think this method can effectively solve cross-vault referencing.
Advantages: Synchronous operation, attachments can be displayed normally, and ![] can be used.
Disadvantages: It is equivalent to making a copy, and images in the canvas cannot be displayed (due to different directory structures).
I have recently looked into these myself.
I am only using git. I’m not a proficient user of git, only have been looking around in this particular area of usage yet. I am also looking for functionality to cross-link vault content.
What I want to avoid is having duplicates of files. Dupes would render linking for me useless. Therefore I am more in favour of symbolic links than junctions.
You can install git with symlink support and you can also add to the config files whether support for symlinks is needed or not. Symlinks need admin rights and/or developer mode turned on (one way to elevate rights; actually, apparently, enabling developer mode removes the restriction of being an administrator).
Currently, I’m only using Obsidian URI links and click the links to open the other vaults at the note referenced.
So basically I’m here to brainstorm or am “gathering confidence” to make the jump into using symlinks, possibly even with a view to using nested vaults.