Hi, I am new here (I am a researcher with intense hobby and they are quite connected). Sorry, this is
a bit long an exciting speculation on planning the workflow. Currently, I log and plan in plant text files. My “everything” log (plain text file in BBEdit) has about 1.73 million words and 153k lines (just from the past in 3 years). From this everything log I regulary (diary or several times a week) copy and past text to different project-specific logs. The limitations of this approach are obvious . I have started to evaluate options (Tinderbox, TheBrain, Obsidian, Devon, TaskPaper - yes, they are quite different.) At the moment, Obsidian is quite attractive for note management. However, after reading some comments on big vaults, one concern is how well Obsidian would serve me if I put all text notes into it (I don’t plan to embed files into the notes, rather just link to them). Will I experience speed issues, even if I do regular book-keeping (removing obsolete notes into project log files) and some organisation? In addition, what is a good robust way of hiding private information when showing and discussing content with other folks? If I use several independent Vaults to avoid one huge Vault, I will have the problem of too many notes related to more than one Vault that justifies this as a concern. Sugesstions that I considered:
- Allow some global folders accessible from all Vaults. For instance, let the Daly notes folder be global and allow some global notes visible from all Vaults. Actually I was surprised that the Daily Notes are Vault-specific. First I created 3 Vaults for different areas, but then I realised that each would have its own separate Daily Notes. This is not how my brain works. Too many of my thoughts/notes are ralated to more than one of these areas. Currently I am copy-pasting such notes from my “everything” text log to several project-specific text logs – takes a lot of time, and using several independent Vaults would not help in avoiding duplicated notes, but globally accessible folder would. I realise this is probably confronting the idea of self-consistent independent Vaults.
- Allow (Mac) OS or special Obsidian aliase (symbolic link) pointing into different Vault folders or notes. I tried to use Mac OS alias, it shows up but if I click on it, it will be opened vie the Finder, that is with BBEdit in my case. Placing in an alias to a folder behaves the same way. It would be nice to open any .md file in my computer in Obsidian even if it does not become part of the active Vault (just for viewing and if I want importing).
- If the above suggestions are not rational to implement, then perhaps the simplest solution (in my view) would be to use a single Vault but with project-specific sub-folders in combination with folder locking/hiding. The content of locked/hidden folders would not be visible for the application. In this way everything can be connected that needs to be, a uniform tagging system is used, and would be no need to duplicate notes, etc. Great benefits. It would also help against the size/speed issue, since blocking/hiding selected sub-folders in a Vault (when focusing on a single project) would gain speed and increase clarity. Once could of course filter out specific folders in searches (also from the graph), but the information is still loaded and managed in Obsidion. However, the contents of locked/hidden folders would not be seen to the app releasing memory and increasing speed. The links into a locked/hidden folder would be seen but could not be activated. Hence, it would also help in hiding private information in a presentation. When activating a link int to a locked/hidden folder Obsidian could show a virtual/dummy link and note such as (locked in)[name of folder], then you could click to go to that folder to unlock if you wanted. The dummy/virtual links and notes would be no real .md files and would be temporary, created only when a link is activated into a locked/hidden folder.
- I have seen some discussion on nested Vaults. Quite interesting option, and I may try it. I could have all private content and everything that is related to more than one specific area (or nested Vault) in the root Valt, and keep all specific knowledge in the nested Vaults (of smaller size). In addition, using a nested Vault with other folks would exclude the possibility of showing private info accidentally. But I would also have the option of seeing things globally. One concern is though that if (in the root Vault) I create a link in a note (in a nested Vault/folder) to a root or neighbouring Vault, that link will point to a non-existing note within the nested Vault. If I accidentaly click on it, will a new note be created (causing confusion in the root Vault) or only if I start editing it? Anyway, this can be done right now, whereas the others are basically feature suggestions.
Anyway, I think I like the 3rd option most - folder locking/hiding -, and please consider it as a suggestion for a new feature.