I think this is the idea:
#+ROAM_ALIAS: provides ‘bi-directional alias’ links. If I have:
#+TITLE: Perceptual control theory
[[Perceptual control theory]] and
[[PCT]] both link back to the same note, and the backlinks buffer populates with ALL references to either one.
Having a ‘uni-directional alias’ is a bit like an index or topic note you’ve made in OR that is pre-configured to show the backlinks from the notes it references (instead of manually writing a search to aggregate them on demand).
So if I make a note like:
#+TITLE: Behavioral science theories
Then the “Behavioral science theories” note’s backlinks buffer would populate with all references to itself, but also all references to
[[PCT]]. However, the “PCT” note’s backlinks buffer would ONLY populate with references to itself (and not also
[[Behavioral science theories]] like it would if you used
If this is right, then uni-directional aliases would basically remove a small step in viewing/aggregating links to topics contained in an index note. Is this right @ClassicRob?
I’m trying to think of the particular benefit this might offer over simply using specific strategies within the existing org-roam capabilities. For instance, you might achieve the same effect if a small function was just added to aggregate the backlinks from a list of other notes.
Would that essentially be the same thing @ClassicRob or is there something more nuanced to it?