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.
3 Comments
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.
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
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.