Capturing activities, collating results

I have “projects” - “topics” might be a better word, identified by hashtag, like “#home/bathroom/remodel”

Things happen related to this topic during the day - emails, phone calls, ideas for Todo items, etc. Multiple topics are active at any one time.

When they happen I open the daily journal and add a bullet list item, with the hashtag, possibly with nested items. Something like

```

- #home/bathroom/remodel Call from [[Acme Contractors]]

- Agreed start date of 2026-06-01

- They will send invoice by end of week

- Confirm invoice received from [[Acme Contractors]] :date: 2026-05-15

```

There are a couple of things I want to do with this data:

1. On a “master page” for the topic I want to create a “Journal” heading that contains just the list items (and any children) tagged with that topic. This gives me a chronological overview of everything that’s happened on this topic.

2. On a “master page” for the topic I want to create a “ToDo” heading that contains just the todo items tagged with that topic (or where any parent list item of the todo item is tagged with the topic). Tasks in this section should be “active” (i.e., I should be able to check them off, change the due date, etc, and this is reflected back on the relevant journal page).

Is this possible? Dataview queries don’t seem to be powerful enough (e.g., forum.obsidian.md/t/dataview-query-to-extract-a-list-item-and-all-its-sublist-items/78291/2), although that discussion is now more than two years old, so functionality may have improved?

If it’s not possible, does anyone have recommendations for ways of working that:

1. Allows me to quickly capture updates on topics without having to navigate through the vault.

2. Collates those updates into a single page.

Check out

There he has areas and spaces but with a little tweaking and understanding the path, template and query structure (and modifying them with a chat bot or you can actually point a AI IDE at your vault, whether in CursorAI or anywhere else), you can have different projects or sub areas and if you feel Dataviewjs is lacking, you can again go forward and in time widen or customize on this foundation, even changing Buttons plugin buttons with Meta Bind ones, whatever.

@Sunnaq445 – sorry, it’s not clear to me why you think that’s a useful answer to the question I posed. I must have missed something, can you be more specific? Thanks.

What I alluded to is that it’s worthwhile to take a look at the structure in the demo vault and if it can be aligned to the expectations enough to make use of the queries, which then can be tweaked with one’s own properties.

A common problem with users is not knowing how to set out or how to create an organic templates – properties – queries structure.
It’s all there in one package to go on.