Thank you, mwra, it’s interesting this hasen’t been requested before.
I use aliases for making sense of the same note in different contexts. Some are automatically created with agents and queries, and some I create myself and place in containers that function as collections that reflect varying criteria of association or classification.
Sometimes I have aliases in different parts of the same container, closer to other notes that share some underlying similarity I’m making sense of.
During my thinking process I often find myself asking “in what other contexts have I previously thought about this note?”. When this happens in Devonthink I can see a list of all replicants in the info pane, including their location in the group structure, and I can navigate to them by clicking on the relevant replicant. In iMapping i do it via right click menu, which shows all equivalents.
This allows me to quickly find and work with related content, but in a way that’s different to links. I use links when I have more clarity about the semantic relationship, and I can express it in some sentence or proposition. I use alises when I’m not yet sure about what the exact relations and all I know is that all aliases under a container have something in common that I’m still trying to figure out. Or when what they have in common is a more complex criteria that can only be expressed with a query agent.
As a way around it, I’ve thought about linking to all containers that have the alias, but I feel this adds unnecesary complexity. I like the distinct functions that links and aliases provide, and I think it would be nice to be able to browse aliases as easily as I can browse links.
I will email the feature request, and I’m still curious if I haven’t thought of another possible workflow or even paradigm.