First, I’d like to thank all contributors to Obsidian for making the absolute best knowledge management application!
Over the years all other applications never quite delivered and ideas of a better system started accumulating in my mind. The most notable idea being able to link anything to anything and use those links as tags themselves. Notion almost allowed this possibility, but not completely. Then Obsidian appeared, making this a reality!
As I’ve become aquatinted with Obsidian I’ve realized that many of my notes are of a particular type or kind. Let’s use Movie for example. For any note that’s a movie I can just add a [[Movie]] link to the top of my file and BAM, that link itself serves as a tag for all movies.
However, all notes that have an “is a” relationship to movie also happen to share a standard set a metadata such as director, run time, IMDB rating, etc. I also want this metadata to be links themselves. The obvious solution seems to be to create a template for Movie that I can apply to all “is a Movie” notes. This does begin to solve the problem of keeping all of the metadata standardized, but it does not solve every problem.
My next thought was for this metadata to be parsable in a way that I or someone else could build a plugin to view all notes that are a Movie in a table just like a Notion database with a standard set of properties. Then I found YAML support for Obsidian which seemed perfect! That is until I realized links do not yet work in YAML front matter. Therefore links could not also serve as the metadata entries.
I’m certainly not the only one that uses links as tags. It seems to be quite a popular trend. The other popular trend for users that use links as tags also seems to be adding links to the top of their notes that’s nearly identical to YAML front matter. This is a VERY common pattern.
I deeply desire the option for YAML metadata to be universally link compatible. I want to build, or see built, plugins that can take advantage of YAML metadata that are also links, while at the same time Obsidian also observes them as links in the graph.
I propose that the syntax could be something like the following and just use the standard backlink formatting already used:
customProperty01: [notalink, randomstring]
customProperty02: [[[isalink]], [[another link]]]
links: [NoteB, NoteC] <-- Similar to "tags", but creates links.