Filtering out Tags without children

Hi,

I am trying to setup a daily journal template. I work with multiple customers and for each customer I usually have a block where the parent is the name of the customer and also a LogSeq Tag.

Example of a usual day in journal:

#CustomerA
  - Child Note 1
    - Child Note 1
  - Child Note 2
#CustomerD
  - Child Note 1
  - Child Note 2
    - Child Note 1

Ideally for this I would like to have a template, listing all of my Customers with the Tag as the parent item (header), example:

#CustomerA
#CustomerB
#CustomerC
#CustomerD

Now, if I do this, due to the fact that it is rare that I need to take notes the same day for all of them, there will be no children for some customers. Which is visually fine. However the problem becomes that the tags will be left there (unless I clean it up manually, which I would like to avoid) and because of that all the days will show up for a certain tag in the hierarchy, essentially making the customer tags useless.

Is there a way to somehow filter out / turn off linking for items where the parent object is a tag and there is no child?

I am also open for alternatives (if any).

Thanks!

Welcome.

  • Filtering is done with queries, especially the advanced variation.
    • It is possible to exclude blocks without children, by demanding to include only those with children.
      • A block with children is one that at least one other block has it as its parent.
  • An alternative could be to:
    • remove the # from all the customers in the template
    • add it manually for each customer that acquires a child

I know and understand that I could do filtering with advanced queries. That said, I am not aware of any way to customize the query behind the graph view for example. Also it would be great to be able to change the default behaviour of this so when I click on a tag, it would not show empty hives.

The Graph view is not very customizable (or functional) at the moment. May give some insight, but cannot be used for real work. There are many relevant Feature Requests.