hello! I believe that we desperately need a new feature. “synonyms”. so that the system can interpret a huge array of names and treat them as one.
for example. instead of creating many files with different names, when we only need 1 file! - we can “hide” a single line in the file where we list these names, separated by commas: “big, large, huge, great, incredible, grand, comprehensive”, and so on.
now when we will look for a file in which we want to add something, we do not necessarily remember - what exactly is the name I called my file?! - no matter what I call it! - starting to enter the name, the system will direct me to this file! - by substituting it in the autocomplete.
I hope I have clearly expressed my idea? if not, please write - I will correct it
You can do exactly what you’re asking for with the “aliases” property.
Example:
If my file is titled “Big”, I can add aliases of large, huge, great, etc. Then, when I’m in a document, I can start typing [[large]], and the option [[Big|large]] will show up, which is a link to the file [[Big]] with the display words large
I don’t think this is a feasible feature. You are asking for a huge thesaurus of common words. But imagine the conflicts when matching words don’t match what a different user expects. (Because they are in a different field, industry, culture, etc.)
And now the search results explode in complexity because many different matches match a word you typed, just in case you happened to mean something else?
I think aliases and defining your own synonyms is the best answer. Also instead of just searching note titles, you can search for content, and insert as many synonyms and keywords as you like, inside the content or properties.
Plus, on the Obsidian Roadmap, better, more relevant search results are planned. Maybe there will be better fuzzy searching, and more expected results near the top.
for this:
we are creating service tags. for example: big, big, huge, great, not fucking, grandiose, comprehensive is a signal to the system that this file has several names at once. I hope I’ve made my point clear. If not, please write, and I’ll fix it.
What is it for? let’s say I have a “nonsense” file, but I can’t remember exactly how I wrote it down (how did I formulate it?: either “nonsense”, or “nonsense”, or “nonsense” (in Russian there are dozens of phrases meaning “nonsense”: “бред, ерунда, чушь, ересь”) and I create ewxe files, even though I don’t need them, because they all mean the same thing. the same thing, that is, they describe the same phenomenon. the only question is the wording. I don’t need a lot of files! I just need one that holds it all.
This could be placed inside the file. Or it could be moved to separate menu files, where you could list all of these files (listed) to be processed as one large file. That is, files: [large], [great], [huge], [heavy], [colossal], [huge] – collected and stitched together into a single BIG.md file containing all of these sections.
Yes, this could be organized (somehow) manually. But it’s awkward and labor-intensive. Understand the logic! We list names that mean the same thing (to us!) and make this known to the system. And the system, understanding this, doesn’t differentiate between [huge], [heavy], [colossal] – all of this is BIG!.md
Right, but how often are you making notes that are titled “big” or “comprehensive”, or other generic small words that would benefit from an automatically-populated thesaurus?
Do you actually have a note called “nonsense”? Is this idea from an actual use-case in your notes? Are you currently having trouble finding a real note in your real vault? Because if so, and you list some real examples, there might even be more relevant suggestions to help make search work better for you.