In Notion, there is no folder structure. Therefore, I can have a page called robot1, and inside robot1, there is a page called system overview. Similarly, I can have a page called robot2, and inside robot2, there is a page called system overview. These are two different pages with the same name.
What I’m Trying to Do
I would like to achieve the same effect in Obsidian using wikilinks. Since Obsidian uses folders, I have a folder named main and another named rest. In the main folder, I have two Markdown files: robot1 and robot2. All other Markdown files, including the two system overview files, are in the rest folder. I want to create a wikilink called system overview in both robot1 and robot2 with text like:
“… blablabla, here is the [[system overview]]. blablabla…”. robot1 and robot2 have two different system overviews. However, Obsidian does not allow two files with the same name in the same folder.
Things I Have Tried
I have read about changing the link display text. It seems I could create two different names and display them as system overview, but I would like to avoid this solution as the file names would become too long. I also do not want to create more folders or subfolders. What I like about Notion is the absence of folders.
The Solution I Wish For
For the two system overview files, I wish I could set a UUID for each file. For example, the first system overview could have UUID 01, and the second could have UUID 02. In the robot1.md file, I could wikilink it as [[system overview:01]], and in the robot2.md file, I could wikilink it as [[system overview:02]], with 01 and 02 not shown in the text. However, Obsidian does not feature like this as far as I know.
Does anyone have any suggestions or alternative solutions for achieving this in Obsidian?
robot1_overview.md
robot2_overview.md
(or any other prefix before overview)
then you embed/transclude the file in robot1, 2 files: ![[robot1_overview]] – if you need to set a display text, you’ll need to think of one on the spot or set an alias for robot1_overview and robot2_overview files in their yaml frontmatter, but that is optional (more work)
you introduce the alt text with | character
the fact that obsidian can have folders don’t much change the equation as you can have a master file and embed headings and even blocks of texts from those master files and assign any display text for them
so you can have
a single robot_overview.md file, where you set up (with heading 2 or 3 most probably) headings: ## robot1 overview or ## overview1 ## robot2 overview or ## overview2
…which you can again embed/transclude in the robot host files, ![[robot_overview#overview1|overview1]] and ![[robot_overview#overview2|overview2]]
you can even refer to blocks of texts with ![[robot_overview#^blockid_to_overview1|overview1]] if you don’t set up headings – notice the different #^ syntax for block id’s which could then be your uuid’s…
First, thank you so much for your speedy response and helpful advice.
The case I introduced is just a toy example. I actually have many similar problems like this. For example, in the main folder, I could have sport.md and math.md, and both of them have exercise.md in the rest folder. As we know, physical exercise is very different from math exercise. However, I really do not want to create a single exercise.md and use headings for physical exercise and math exercise since they are very different. I also really do not want to create two files named sport_exercise.md and math_exercise.md. In my actual problem, this approach would result in very long filenames with over ten underscores (_).
Another example is having dog.md and harddisk.md in the main folder, both linking to health.md in the rest folder. As we know, dog’s health is very different from harddisk’s health. I guess you know how the story will go.
You may wonder why I want to do this. Actually, humans often overload words with multiple meanings depending on the context. This is the most nature way for me to do, instead of making the name of the file longer and longer, which is not nature for me.
However, thank you for your help. I am very grateful.
