Search based on parent field value

Explain the problem as you see it

Two examples:

for a recurring meeting, I want to always see tasks associated with the meeting type as well as all tasks related to the attendees
Two explore related concepts that share the same filed cannot be directly shown

Why is this a problem for you?

I can't truly explore connections within my graph.

Suggest a solution

Enable the use of field input of the parent as search input of a search node. If there are performance constraints, a run-once might be sufficient, too.

⁨4⁩ ⁨comments⁩

⁨4⁩ ⁨Comments⁩

Imre Vogelezang

Mar 4, 2023

This is similar to descendant queries, right? I would like to use this for my journal entries. All my journal entries have a question with a reference, answers are children of these questions. I would like to list the answers (children of a question with a specific reference), without having to type and write in a field of a super tag.

Carl Joseph

Mar 4, 2023

Is it only the parent that you want to use in the search criteria? I just put in an idea for something similar, but to use any other field/attribute as part of the search/WHERE clause.

I can remove mine if this idea covers that similar use case

Mattias Petter Johansson

Jun 30, 2023

YES, this would be so incredibly useful to me, I am denormalizing a lot just to get around this at the moment and its making my views very noisy.

John Hildenbiddle

Apr 2, 2025

Upvoted this idea instead of creating a new one due to similarity.

My goal is to display the following as related content or all #meeting nodes:

Show #reminder nodes
that LINKS TO
Every #people reference in the >Attendees field
Grouped by the #people reference

The end result might look something like this:

REMINDERS

Bob
[  ] Do this #reminder
[  ] Do that #reminder

Sam
[  ] Do this #reminder
[  ] Do that #reminder

I can almost get this working with the following query:

#reminder
LINKS TO   PARENT.Attenees
NOT        OR
             PARENTS DESCENDANTS
             DONE

The issue is that Tana currently only matches the first #people ref in the attendees field. As a result, the query returns only #reminder nodes for the first attendees in the list (which also breaks if I am the first attendee in the list). Tana should match all items in a field, not just the first.