Andric Tham

Explain the problem as you see it

Sometimes a link matters more as an outgoing link (to add context) than it does as an incoming backlink.

To avoid cluttering the references section under any given node, let me hide incoming references to any given node that are irrelevant so that those that I can see only those that are relevant, which speeds up the way I navigate through my Tana workspace(s).

Note: While I’ve encountered this problem most recently while I’m using Tana for learning, this is equally valid in other use cases I’ve used Tana for, such as collaborative project management and research, where there are many-to-one relationships where the “many” side can be really noisy.

Why is this a problem for you?

I have a Tana workspace where I store references (i.e. tutorials, code samples, books, videos, etc) to certain topics I’m learning.

Sometimes, a reference is directly relevant to the topic I’m learning. Other times, it’s only relevant in context of another topic.

For instance, this tutorial might demonstrate integrating with Supabase and Prisma. In this context, the use of node.js, Typescript, and PostgreSQL is only tangential. The resource is really trying to teach Supabase and Prisma.

I still want to link to node.js, Typescript, and PostgreSQL inside of a field so that I can see at a glance what technologies this tutorial is teaching, but I do not want to see the reference to this tutorial when I’m viewing the node.js, Typescript, or PostgreSQL nodes in full-screen, for in those contexts, it’s not highly-relevant. I might want to see tutorials that specifically teach those technologies, instead.

Search nodes are not a solution to this, as they filter on nodes by explicit inclusion criteria, rather than implicit or explicit exclusion criteria. More on this below.

Suggest a solution

In the “References” section that shows up when you are viewing a node in full-screen:

• Let me hide certain references (implicit exclusion)
  • The exclusion criteria is implicit because I only know something is irrelevant contextually. It cannot be inferred from any fields that are on the incoming reference.
• Let me filter out certain references based on certain criteria (specified as exclusion criteria, rather than inclusion criteria like Search Nodes)
  • Why exclusion criteria? It’s easier to tell if something is low-signal a posteriori (after the fact) rather than a priori (before the fact). So, let me filter out irrelevant references, rather than search for relevant references before I know what might or might not be relevant.