@User the mental model I had in my head for vaults (and its not set in stone) is that a hierarchy could exist spread across multiple vaults. each vault is a github repo. you can there fore have a

public

vault and a

private

vault and you can choose to share everything in one but nothing in the other

what's nice about this model is that you still get to have one unified hierarchy that can span any number of vaults

the links might be somewhat problematic in case of name collisions; with foam there was thinking that collisions should just trigger error diagnostics. Especially if the structures are merged and they spawn from the root without a prefix, that might be the only reasonable option

especially if you first use vault A without a prefix, all the links would already be there without prefixes - only after introduction vault B (and C and D...) the conflicts might appear

still to note: maybe the vault B is developed first separately, thus its links also being without any prefixes - now bringing these two together would start creating the conflict errors

for links that conflict, why don't we just show all matches for an unprefixed link? if no conflicts, have the same behavior as today but if conflicts are detected, ask user to detect. need to head out to lunch so will resume this conversation after.

"why don't we just show all matches for an unprefixed link" - this would work inside vscode, but if the user just publishes the workspace with conflicting vaults, I guess the link must point to some single pre-selected place(?). Also, I think the intent behind the link is to point to a single location, so asking user to fix it would probably be reasonable.

There's probably all kind of complex scenarios that we could envision (e.g. what if the user would like to merge domains across vaults and show all merged notes in the published page as a merged web page?), but then again 99.9% of the real cases probably just want to use multiple folders and avoid conflicts. Showing errors would probably be the easiest and still sufficient solution.

@User coming back to this thread. agree with your conclusion. the other solution would be to generate a popup/intermediary page for links with multiple destinations and let the user choose. e for v1, would bias for what you suggested and error at build time.

I would like to link books (which are in the root folder) into my notes: how should I do it? Should I use []() notation? Or something like [[]]?

You'd wanna use this:

[[Books|books]]

, the syntax is:

[[Label|path.to.note]]

are the books markdown files, pdfs or something else?

They are pdf's

Oh, then disregard my message

They were all included into the top folder

With the # Imported Assets tag

I think [[some-book.pdf]] should work, especially if you have pdf viewer installed into vscode

Oh, they are inside assets

From the docs:

[local files](assets/think.pdf)

Reference: https://www.dendron.so/notes/3472226a-ff3c-432d-bf5d-10926f39f6c2.html#other-links

@User that might be better way to do it, yes

I've actually slammed a few non-markdown files into my vault, using the same naming scheme with them (e.g. excel files)

then using the [[...]] syntax + "Open in Application"-extension I'm able to get them open from vscode

not sure if that's something I actually shouldn't do 🤔 😆

Is it possible that I have too many things inside root that the auto complete isn't working?

I wouldn't say openning an excel file inside vs code would be a better idea though

pdfs might not show up in the lookup

> Is it possible that I have too many things inside root that the auto complete isn't working? @User can you elaborate?

I'm trying to use [label](assets/*.pdf), but when I am typing the book name it isn't filtering. For example, I was trying to link "Statistical Learning in R" using that syntax. While I was typing "statistical", it wasn't filtering anything (it was actually showing me every file of assets/ in alphabetical order, I think)