Noting Meetings

Questions & Help
,
2

Short answer: All of your points have their place.

Long answer: There is no established best practice, neither among note-keeping applications, nor within Logseq’s community. Learn from others, but develop your own approach. Below is my own take on it.

  • Hierarchies are for strictly hierarchical things, not for organization.
    • Most relationships are not hierarchical.
      • Their structure should emerge within the graph.
    • For local hierarchy needs, use the normal indentation of the outliner.
      • This covers the majority of the cases.
    • Don’t put your pages into fixed hierarchies, unless some pages are really subpages.
      • Even in such cases, consider merging the subpages into their parent.
    • Projects are hierarchical as long as they can be broken into subprojects.
    • Meetings generally don’t participate in hierarchies themselves.
      • The outline of a meeting is perfectly served by indentation.
      • This is essentially your point 1.
  • Daily Agenda is for keeping together same-day events.
    • Almost everything begins there, because almost everything takes place in time.
      • For some applications, it is ok for their notes to remain in journal forever.
        • This is useful only when the notes are consistently tagged.
          • Otherwise it is a mere calendar.
        • This is essentially your point 2.
      • For serious knowledge management, most notes should be moved to dedicated pages.
        • This should happen when ready, i.e. confident enough about the destination.
    • Projects totally deserve dedicated pages (sometimes even graphs).
      • Journal should still keep track of their events, by referencing the respective project.
      • This is essentially your point 3.
    • Meetings take place in time, so they are excellent candidates for journal.
      • If a meeting needs complicated organization, it deserves its own page.
        • Journal should still keep a reference to the dedicated page.
5 Likes