Simple Query
Type a filter, get a view — one that keeps itself current, instead of a table you keep updating by hand.
- ··A query is a filter line (type:meeting, status:open), not a formula and not a spreadsheet.
- ··The view updates itself the moment a block meets the criteria — nothing to enter afterwards.
- ··The same query becomes a list, a table or a board: one source, three views.
Transcript
What if your overview were not a snapshot that ages from the moment you save it, but a view that keeps itself current? That is the whole point of the Simple Query, and over the next few minutes you will hear why one filter line does more for you than any table you keep updating by hand.
Cmd+K finds a single block. A query holds that finding in place. You describe once what you want to see — say every meeting whose status is open — and from then on mium shows you that view on its own. Instead of a table you feed, a filter line that thinks along and fetches the answer afresh on every look.
A hand-maintained overview is always a snapshot. The moment you save it, it begins to age, because every new block and every status change would have to be entered by hand. In day-to-day work that rarely happens in full, so the table soon shows the state of a fortnight ago. A query turns this around, since it re-queries the existing set on every glance — the view is always of right now.
A query is not a formula editor, it is a plain filter line. You name a property and a value, and only the matching blocks appear. When a block meets the criteria it shows up. When it no longer does, it goes away. Nobody enters anything afterwards, because there is nothing to enter.
The same query becomes a list, a table or a board. You choose the view, the data stays one single source. For the standup you show the board, for reporting the same query as a table — no copy, no second round of upkeep. The truth sits in the blocks themselves, not in an extract that goes stale the moment it is made.
One honest catch remains. The filter axis is your properties, so you can only query for what you actually maintain as a property. The upkeep does not vanish entirely; it shifts from the table to property discipline — and that is the one place a query stays empty if you neglect it.
The honest question at the end: how many of your overviews are truly current today, and how many show the state of a fortnight ago because nobody updated them? A saved query lives as a block on a page and keeps itself of right now. Search once, see it for always — your second brain gives back what you entrust to it.
Cmd+K finds a block. A query holds that finding in place: you describe once what you want to see — and mium shows it to you from then on, on its own. Instead of a table you maintain, a filter line that thinks along.
Why tables go stale
A hand-maintained overview is a snapshot: the moment you save it, it begins to age. Every new block, every status change in the existing set has to be entered by hand — and in day-to-day work that rarely happens in full. A query turns this around: it re-queries the existing set on every glance, so the view is always of right now.
5 rules for Simple Query
- A query is a filter line, not a formula editor — type:meeting, status:open, autor:team-mut.
- The view is live: when a block meets the criteria it appears; when it no longer does, it goes away.
- The same query renders as a list, a table or a board — you choose the view, the data stays one source.
- Properties are the filter axis — what you don't maintain as a property, you can't query for.
- A saved query lives as a block on a page, not as an external dashboard — it is part of the knowledge.
What a query looks like
{{query (and (property "type" "meeting")
(property "status" "offen"))}}
;; Ansicht: Tabelle · Sortierung: zuletzt-geändertBefore and after — table vs. Simple Query
| Step | Hand-maintained table | Simple Query |
|---|---|---|
| Setting up | define columns, type in rows | type a filter line |
| Keeping current | enter every change by hand | keeps itself current |
| Switching the view | build a new table | switch list / table / board |
| Source of truth | the table (a copy) | the blocks themselves |
| Upkeep | ongoing | one time (the criteria) |
An honest question
How many of your overviews are truly current today, and how many show the state of a fortnight ago because nobody updated them? The answer decides whether an overview takes work off your hands or becomes one more thing you have to maintain.