Here’s your query.
Important notes :block/name is the lower-case name of a page. When you use namespaces, it will get everything referencing the namespace regardless of what level of the namespace.
So project gets Project, but also Project/Personal.
project/personal will get Project/Personal and also Project/Personal/test, but not Project.
See the screenshot I added
Thank you so much — this is super helpful! I guess I need to start learning advanced queries much better to beef up my workflow.
One thing I forgot to mention in my original workflow - sometimes I tag the task directly rather than nesting under a tag (see last meeting example in this screenshot). Any chance you can help me modify the original query to get these tasks as well? (Your query currently returns the tasks from the first two meetings, but does not return tasks from the third meeting in this screenshot)
This goes from relatively simple to relatively complex pretty fast.
First of :block/refs doesn’t get what you need.
Also you want the block on the page and not the parent of the block, though in this case that is the same, but if your task is under a parent block you won’t retrieve it.
Next getting a namespace is only 1 level deep, and here’s where the complexity comes from.
I’m going to assume you don’t want that to be static
So I use rules to create a recursive search to find all pages under project, no matter their dept.
Here’s the query I created:
Yes. :block/name is always lowercase. I forgot to mention, I generally add that for clarity!
Pages have 2 names, one is lowercase and stored in the attribute :block/name and the other is their original name case stored in :block/original-name.
I generally use :block/name so we don’t have to think how exactly we wrote the name of a page
For filtering priority we have the attribute :block/priority
So we will need to add the line: [?b :block/priority "A"] to the query.
Alternatively we can do this the same way as we did for the task itself.
Hi there @Siferiax , many thanks for the solution… its nearly perfect.
If you allow one last question:
Sometimes i would also note some tasks in the root layer of a namespace (“project/…”).
Is it possible to include these tasks with priority into the query results?
i already found the great Query-Builder-Tool from adxsoft
but couldn’t figure out how to build a recursive query for the namespaces like the one @Siferiax provided. Maybe its just a matter of time learning the nuances of datalog.
For now the hints from Siferiax provides a very powerful solution for project management in Logseq.