From a question on the Logseq forum: Creating a Resonance Calendar from queries
A resonance calendar is taken from a video created by Ali Abdaal How I use Notion as a Resonance Calendar - YouTube. It’s a list of interesting (resonating) resources, added to your notes. Resources can be one of:
How to implement this in logseq?
This is a fairly straight forward query:
- line 6: take the page properties of
?page(set in line 3) and store them in
- line 7: of all the different properties, take
:typeand store it in
- line 8: check if
?typeis one of: movie, article or book
Important: book !=
[[book]]. Don’t use
[[book]] in type.
New are the line 9 to 12
line 9: a not statement, everything that matches this query will be excluded from the result
line 10: again, a page property
line 11: but this time we search for
:ratingand we match it with
line 12: close the
Result: same list, but without the ones rated
For fun you can invert the search, only show the ones rated
This query is simpler then the previous one,
and is implied, by default all lines should be true. Logseq is a very positive program 😄.
It’s not just
1/10 that’s bad, so is
2/10, but adding that is not as simple as you would want:
Notice line 12 the
contains? statement is quite complicated. This is because
2/10 are really
[[1/10]] and [[2/10]]. They’re not just text, they are searchable items. This is different from
type in Resonance List 1, line 8.
But what if you would like to have a tag that shows how terrible the book or movie was?
tags:: [[terrible]] (or just
terrible, if you never want to list them, just change it accordingly in the listing below)
New are the lines 13 and 14, we exclude
[[terrible]] from our list.
If you want to add more tags, then look at Resonance List 3 how to do that.
Logseq’s search functionality is not as easy as one would wish for, but it is adaquate, and can be made to search for the data you’re interested in.