I am copy/edit here where we stand currently from the archived thread. Then, I’ll add some remarks.
You can add your custom attributes in the YAML frontmatter but:
-
They MUST be in proper yaml format.
-
If an attribute is not handled by obsidian or plugin, it will be ignored. But still has to be YAML format.
-
The YAML frontmatter is not scanned when searching for unlinked mentions (and probably never will be). That is, if NoteA has this frontmatter:
---
connections: [NoteB, NoteC]
---
NoteA will not appear as an unlinked mention in NoteB and NoteC.
- There is no support (yet) for adding a linked mention to another note, that is, if NoteA has this frontmatter:
---
links: [[[NoteB]], [[NoteC]]]
---
It will not work. NoteA will not appear as a linked mention (backlink) in NoteB and NoteC.
If at some point we add support for linking other notes in the YAML block, it will be specific and limited to a YAML attribute, like related: . But it still won’t be possible to add linked mentions in other attributes.
Remarks
Thare is an interesting dichotomy between the YAML block and the rest of the text.
The YAML block is meant for database-like approach: highly structured data that is handled by specialized software.
Obsidian, and tools like it, were born under the idea of using unstructured plain text data (or not so structured) and rely exclusively on connections and search/filters.
You can solve many productivity problems using either approach. Some workflows look cleaner with one or the other.
Now back to your proposal, you can either 1) write a plugin to explicitly handle your movie data or 2) put it in the main text, perhaps in block right after the YAML block, and rely on Obsidian linking engine.
---
# YAML BLOCK
---
# Your Block
___
(Edited Example)