You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature]: Use frontmatter aliases in search and link suggestions #2288
People and organisations go by many names: a full name, a nickname, an acronym, a transliteration. We keep one note per entity with Obsidian-style aliases in frontmatter, which OpenKnowledge preserves. As far as I can tell from the docs, search is title boost plus body BM25 plus recency. So an alias only finds the note if it also appears in the body, and I couldn't find aliases mentioned for link autocomplete. If this already works, a docs note would be enough.
Proposed solution
Search (the omnibar and MCP search) matches aliases the way it matches titles.
Link autocomplete offers a note under each of its aliases, writing [[note|Alias]].
Optional: [[Alias]] resolves to the note when exactly one note carries that alias and no note has that name or path. A note's own name always wins, so links that resolve today keep resolving the same way.
What would you see if it worked?
A note orgs/un-refugee-agency.md with aliases: [UNHCR, HCR] ranks like a title match for the query "UNHCR".
Typing [[UNHC suggests it.
Area
MCP / agent integration (search is shared with the omnibar)
Alternatives considered
We repeat aliases in the note body. It works for search but duplicates data that drifts, and it doesn't help link suggestions.
Activity