#26

My main issue with them being used across nested vaults is in the case that the nested vaults are being shared with collaborators who don’t have access to the parent vault. I don’t like the idea of creating a lot of mess in a shared vault by leaving stray ^blockIDs everywhere; it feels selfish.

The only way I can think of to reconcile this would be to have custom CSS that hides the blockIDs, but this would need to be adopted by every collaborator. This could also be used in a publish.css file to hide broken blockIDs on a nested Publish site. Would be curious if anyone can think of any downsides to that approach.

2 Likes
#27

got you that’s an interesting approach. I havn’t yet used obsidian for colloboration, but I do see how having a lot of blocklinks that lead nowhere can cause clutter.

#28

Hi, this thread is probably a bit too advanced for my basic beginner’s question, but there’s something I don’t understand, so I’m calling for help!
I’m currently in the process of setting up my folder structure.
But:
If a vault “consists of a folder, and any sub-folders within it” (says the help), I deduce that it is not recommended to create a sub-folder structure within a vault?
Because when I look at the only vault I’ve created so far, it’s just a folder in my finder, located where I decided to put it…

#29

@gsf: you can safely create subfolders in a vault because those subfolders are not vaults.

#30

@Klaas : Thank you, but just to be sure: with no limit, or just one-level ?
(then a vault isn’t just "a folder, and any sub-folders within it”, and has other specificities and characteristics, then, I guess)

#31

@gsf: I don’t think there is a limit on levels. I have not tried nested vaults, but I think a vault is a folder with a CSS file in it.

1 Like
#32

ahh yeah no worries @gsf you can have infinite amounts of sub folders inside your vault.

Nested vaults are something different in concept. they just mean that one choses to go to the “choose a vault menu” and choose a sub-folder and treat it as a vault.

that is completly optional and not needed for most users

folders vs vaults are confusing

by default think about everything as a sub-folder in Obsidian, create as many sub-sub-sub folders as you want.

you will know you created a new vault only when you go to the vault menu and deliberatly create a new vault out of a folder in your computer.

Let me know if that helps, and if you have any questions just let me know, happy to help

2 Likes
#34

@gsf: your clicked on the reply button to me, but replied to Santi :wink:

#35

@santi Thank you I think i get the difference now! Ok, but I will try not to have more than three sub-folders levels!
I’ve really immersed myself in using Obsidian because I’ve been wanting to centralize my notes for years, and this is the time (and the tool). I find it so good that I paid to support the development of the application.
Now I need to explore the potential of linked notes.

So I’m taking advantage of your proposal, I have another question that’s still as basic: I created my first vault a little bit quickly as a test, but in the end it’s getting more and more structured and I’m really using it, but I chose a name a little bit quickly, can I rename it as simply as you rename a folder in the finder? Thanks in advance.

#36

@Klaas Fixed! :wink:

2 Likes
#37

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
#38

@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
#39

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
#40

@santi …but, that would be like making a vault inside a vault, which is not recommended, if I understood correctly?

1 Like
#41

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.

Nested Vaults (vault within a vault)

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

#42

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
#43

sounds good, feel free to ask questions if you ever need help with this in the future!
Good luck @gsf

1 Like
#44

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
#45

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.

#46

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.

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.