Hello,
I am trying to build the following logic to capture my running task of the day.
I can make it as separate queries, but it’d way easier to join it into a single one.
Idea is to get:
(anything with #tod tag AND not done)
OR (anything that is scheduled for today or prior AND not done)
OR (anything that is having DOING status)
Extrapolating the query example I am building on, it seems that the more I add analysis paths (ie linking to marker, name, schedule info) the more it assumes them as mandatory in my dataset and limiting the output. A bit like similar to using INNER JOINs in SQL.
Any idea how to create multiples analysis path more like LEFT JOIN ? Ie, is there is not scheduled info, still keep the block.
Hello, would you help me out to tell how you write the query “anything that is scheduled for today or prior AND not done” (as an individual, separate query like you’ve mentioned in your post).
@Simeonh2021 this is a simplified version of my original attempt.
For (SCHEDULED TODAY||PRIOR) && (NOT DONE, NOT CANCELED, NOT LATER) it would be something like below.
Logic is
Get all scheduled => [?b :block/scheduled]
See if they have a status, if so filter over it => [(get-else $ ?b :block/marker “NIL”) ?marker] …
Filter by target date => [(get-else $ ?b :block/scheduled ?today) ?d][(<= ?d ?today)]