Comment by ezst
21 hours ago
> I've noticed that trillium has hierarchical notes; is there a view to look at an item higher on the tree and have it also have the contents of all its children?
You are right that the "atom" of content is the block in an outliner and the Note in Trilium. If you can tolerate⁰ the coarser-granularity, you can make Trilium behave pretty closely to an outliner: notes can be embedded within notes, either manually, or via the "Book" note-type¹ (that essentially renders a tree as embedded notes), hoisting² should be a familiar concept then.
⁰: when researching the topic, I immediately fell in love with outliners, thinking I would never go back to a note-based approach like Joplin which I was using then, but here I am, promoting a note-based solution. Metadata/tags at block level is not something I could get the hang of (I know how to manage collections of notes at scale, but not collections of blocks). ¹: https://triliumnext.github.io/Docs/Wiki/book-note.html ²: https://triliumnext.github.io/Docs/Wiki/note-hoisting.html
Book is exactly what I was thinking of!
I think my only other question is around my preferred "Daily Journal" workflow and unreferenced tags
On one hand I feel some surprise that you're noting a distinction between metadata/tags for collections of notes vs collections of blocks. On the other hand, it's a bit of a peeve of mine that there's a distinction between "pages" and "blocks" in logseq when it comes to linking & referencing.
> I think my only other question is around my preferred "Daily Journal" workflow and unreferenced tags
how do you generally go about that? Trilium has the concept of day notes¹, incrementally building a time-structured hierarchy (years/months/days, but you can configure that however you want), under which you can park your notes. Or you can just let them stay unordered under an "#inbox"² for later categorisation. It's up to you.
My workflow include both time-based (log of events on that day, meetings and appointments happening on that day, etc), and time-independent notes (notes on projects, places, etc), and I have essentially 3 top-level hierarchies:
- Journal ← time-based
- Hierarchical notes ← time-independent
- Reference notes ← collections of things being often referred to
(and I have a workspace³ for Personal-stuff and another for Work-related-stuff, but the Reference notes are "cloned⁴" - and hence accessible ‑ in both).
Interestingly, "Book" recently gained a "Calendar" mode, so you can very easily manage notes as events as well, move them from day to day, etc.
> On one hand I feel some surprise that you're noting a distinction between metadata/tags for collections of notes vs collections of blocks. On the other hand, it's a bit of a peeve of mine that there's a distinction between "pages" and "blocks" in logseq when it comes to linking & referencing.
At least it's consistent in that Trilium always holds metadata/tags at note-level. And using Inheritance⁵ and Templates⁶, you can guarantee that all your Reference notes are consistent in terms of type of metadata they hold (all Persons have a "born in" attribute, etc). At the moment I'm working on an extension of the "Book" note type to enable bulk metadata edition in an ag-grid control, effectively managing metadata like a database (not unlike what exists in Notion, but with composition/inheritance and proper sum types).
¹: https://triliumnext.github.io/Docs/Wiki/day-notes.html ²: https://triliumnext.github.io/Docs/Wiki/attributes.html ³: https://triliumnext.github.io/Docs/Wiki/workspace.html ⁴: https://triliumnext.github.io/Docs/Wiki/cloning-notes.html ⁵: https://triliumnext.github.io/Docs/Wiki/attribute-inheritanc... ⁶: https://triliumnext.github.io/Docs/Wiki/template.html