@Klaas Fixed! 
2 Likes
ahh cool I was just about to show you how, there are no problems renaming vaults, they just have to be selected again from the “vault selecting” main menu (for anyone else who might read this)
And yeah I do believe Obsidian is a perfect tool for putting together all notes, the fact that it’s markdown plain text files makes a huge difference for future proofing.
1 Like
@santi
About the vaults, I thought of something:
Let’s say I have a vault with all my research work.
And inside, a folder with a set of notes that I use most often. So I can’t just open in Obsidian this set only (because that would be equivalent to a vault within a vault, I suppose)?
That would have been convenient, so as not to force Obsidian to open the whole (and the heaviness!) of the whole set.
1 Like
yeah that would work and it’s a good idea of you want to have a small vault to deal with.
However I wouldn’t worry about number of notes, if that’s a worry for you I use my vault with over 1000 notes and I have 0 issues with it.
But if you ever feel Obsidian going slow with larger vaults, what you proposed it’s a great idea
1 Like
@santi …but, that would be like making a vault inside a vault, which is not recommended, if I understood correctly?
1 Like
it’s not recommended mostly for the fact that it might not be compatible in future versions. So far there are no issues (that I’m aware of)
A Vault within a vault is only a way to open a subfolder inside another vault, and open that subfolder as it’s own vault (from the opening vaults menu)
I also wrote another post on this if you want to see more disccusion on it.
I would say, if you don’t see an obvious need for using nested vaults in your system, then perhaps you don’t need them. it’s not a bad idea to avoid them, since we don’t know if future version of obsidian will support them
Thank you, yes I will read this because it is interesting for the use of Obsidian.
I have imported a very large number of texts and notes into Obsidian, and for the moment I don’t see any slowing down, we’ll see as we go along though…
So if this continues without slowing down, I’m not going to do nested vault at least for the moment.
1 Like
sounds good, feel free to ask questions if you ever need help with this in the future!
Good luck @gsf
1 Like
I support the continued viability of nested vaults. I am creating online courseware with Obsidian. The student vault has lessons linked to references etc. The parent faculty vault has additional things that I want to prevent students from seeing, such as notes to prof, test questions, and developer notes. 2 sites are published, faculty sees all, students see a cleaned up version. Linking from student site into faculty stuff is prevented. Works just great, would like to keep this functionality.
3 Likes
I just started to create my “second brain” and wanted made two vaults, one with unedited\sources\origins\notes to store articles and others.
And second vault where I will work with my thoughts and make links to sources.
At first wanted to create two different vaults next to each other, but I found I can’t make links to outside vault. So second thought was to create nested vault.
Thanks to all of you for yours replies.
But I was confused by the following situation.
@Daedren
One thing I know: If I have two notes of the same name in the two vaults and the nested vault has a note with a link with that name, inside the nested vault it links to the note of the nested vault while on the main vault the link points to the note of the main vault, not the one originally linked to inside the nested vault, although it can also see it.
So, relative link format will fix this situation, wont it?
I mean, if you have structure like:
MainVault:
–Note1
–Note2
–NestedVault
----NestedNote1
----Note2
And in this case for NestedNote1 relative link to Note2 will be [[Note2]]
For Note1 link to Note2 in MainVault will be [[Note2]] and to NestedVault Note2 will be [[NestedVault/Note2]].
Correct me if I am wrong.
I use nested vaults to represent concentric circles of access control, so far with good success. Eg with the following four nested vaults:
- notes/ - private home-machine-only content, never synced via cloud, plus…
- notes/cloud/ - private synced content, synced via encrypted cloud, plus…
- notes/cloud/public/ - public content, mirrored to website, plus
- notes/cloud/public/blog/ - published content, announced in rss feed.
- notes/cloud/public/ - public content, mirrored to website, plus
- notes/cloud/ - private synced content, synced via encrypted cloud, plus…
and a bit of website scripting: when on your home machine, you can see everything. When on your phone, you see the smaller cloud-synced subset. Anyone with a web browser can see the smaller public subset. Anyone subscribed to your blog feed sees the new content in the smaller blog subset.
4 Likes
Periodically you can review new/edited pages to see if they should be moved to a different (more or less private) vault. In such cases you simply move the file, and your vaults mostly just keep working - a great feature of Obsidian. (Moving a page up to a more secure vault will break links to it in the less secure vault - not a problem. Often splitting the page into two is a good fix.)
Another level suggests itself: notes/cloud/groups in which each of your collaborators has a vault where they only have edit permission, and in which they can read the vaults of others group members and link to their notes. The author or anyone else reading the note can then follow the backlink.
1 Like
Hi @Ellanxis, I didn’t see your post before.
I’ll try to clarify what I meant. It was actually just a heads-up from back when people were extremely vocal about the atomicity of notes and even naming the note as the content of its thought.
So, if you’re writing a set of notes in the nested vault and make links and one points to a note named “name”, the link will be [[name]], which is also in the nested vault.
But then you open the main vault, which also has another set of notes on its level with a link [[name]]. If you surf your nested vault from the main vault, when you click the link from the nested vault, you’ll be directed to the “name” note of the main vault, not the nested one, as it should be.
Note (no pun intended) that the nested vault is never aware of the [[NestedVault/Note2]] relation. The same if you try to link something from the main vault to the nested vault and then try to open it from the nested vault. It tries to create a new note.
This is a very specific problem that is present in very, very few scenarios if any. It is very simple to solve, if you ensure you have unique names for every note across all vaults and between them too.
I hope I was able to clarify it.
any updates or changes to best practices here?
i’m currently doing my “nesting” in DEVONthink— i have like six vaults for Obsidian and then i index them all in DEVONthink in a designated DEVONthink database. this means i can work with my notes really fast regardless of how pokey Obsidian is being. i toss tons of markdown/pdf/bookmarks/articles into my DEVONthink inbox and then slide them into Vault folders as appropriate.
if i do cross-vault linking inside Obsidian it works, but i do easily end up with duplicate files and i might write something my research vault but then when i am processing my notes after a workshop i’ve facilitated. part of that are binary files that are artifacts like architecture diagrams, screenshots, that sort of thing. nesting and alias/linking would be great but i am reluctant to even attempt nested vaults.
the DEVONthing abstraction layer (well it’s a lot smarter than just random middleware i am really loving the plugins for pulling related docs from DT into my Obsidian notes, that sort of thing.
but i’m starting to get frustrated with the materials being duplicated and being difficult to track revisions to some notes or documentation or research material. it’s not the size of the data that concerns me (if it gets really top-heavy i have some options in mind) as much as the clutter and being unable to know if this is the right copy of a print-as-PDF Confluence page, or Excel and Word docs.
the idea of the sub-vault of sensitive data that needs to be available on the go. i use DEVONthink to Go (it’s been a rocky road but we’re in a good place right now) as my information retrieval and triage front-end for collected and captured things.
Well I’ve been using nested vaults now for over two years. They have become progressively more extensive and the hierachy has extended further up and down. I don’t have any vaults outside my nested system (apart from occasional test vaults) and I have experienced no problems whatever. The warnings in the early days came as a response to developer concerns with often strident warnings from moderators. My feeling is that most people would have no issues; that recovery from any issues that people somehow stumbled into ought to be straightforward. The risks are certainly much lower in terms of data loss than most of the sync solutions people use.
But the issues remain the same. Thoughtlessly accepting offers to create a new file from a link without being aware of where you are brings the possibility of filename clashes in some higher level vaults. This will never happen if all files are given unique names.
My vaults now routinely have their own folders for attachments and linked files. I make extensive use of the nested folder system outside Obsidian. Every one of my projects has a vault, some even have sub-vaults nested within them. Fleas ad infinitum.
I’m not sure I even partially understand your system, and I don’t use DT. But it seems that the problem arises thorough the interaction between your info in DT and your info in Obsidian. I don’t understand it well enough to give advice.
But I would suggest routinely adding date/time to your file names - that should at least let you identify the most recent. (I routinely use a text expander.)
It ought to be simple to use a file comparison program to identify and delete duplicates (you would need to check each deletion manually, since I suspect that you create possibilities for the most recent file not to be the most complete).
3 Likes
oh i’m a compulsive annotator and any output is named zettel-style. i even made a textExpander macro to do a current date-time-stamp dts and i wrote a Finder action to rename a file so i click that thing whenever i want an atomic incarnation of a file that is easily usable and retrievable by using that chronological order.
thank you for your reply! i tried to do a submodule of a repository and they don’t propogate when using Obsidian Sync. ordinarily that wouldn’t bother me and i’d use Resilio to p2p sync between devices.
but every time i’ve got a sync problem the first thing everyone on discord says is to stop using anything that isn’t a local saved vault on a computer using Obsidian Sync. i’m still testing, the real source of truth is DEVONthink.
I don’t completely understand your issues.
But, on your main device, you can select a subfolder of your main vault and open that as a new vault. The contents of that vault would be synchronised by Sync with the main vault. You should be able to open it on any device.
I don’t use Sync, so I’m not sure of which settings you would want to use. You could sync both vaults but I suspect that would open up the possibility of Sync clashing with itself.
I’m sure there is a simple solution, even using Sync, but can’t advise very well. It would be important to get the structuring of you nested system correct, if you want to sync some vaults but not others.
Are nested vaults fully compatible with Obsidian sync? i.e. no conflicts when syncing multiple vaults which are nested together.
So if my vault set up is like this:
master-vault/
- nested-vault/
and both vaults are being synced with Obsidian sync, are there any scenarios which might cause undesired behaviour?
an edge case I can think of is
- editing files in nested-vault whilst in master-vault, and then editing those files again on a different device and vice versa
No, this is not supported. In fact if both vaults are open and syncing at the same time you might see race conditions between the two vaults, leading to duplications and deletions, etc.