-
-
Save dannberg/7617aa7f4198938352431b7a9f77f8d1 to your computer and use it in GitHub Desktop.
[[+Home]] %% tags:: #MOC %% | |
# Meetings MOC | |
Meetings are timestamped events with other people, where information is exchanged and collected. Meeting notes are intrinsically ephemeral. They're stored in a separate Space than other Umami notes (`Timestamps/Meetings`) and rarely reviewed. If there's information in a meeting that needs to be accessed later, it should be moved into a more evergreen note in the Umami folder. | |
**Template:** [[Template, Meeting]] | |
```meta-bind-button | |
label: New Meeting | |
hidden: false | |
class: "" | |
tooltip: "" | |
id: "" | |
style: default | |
actions: | |
- type: templaterCreateNote | |
templateFile: Extras/Templates/Template, Meeting.md | |
folderPath: Timestamps/Meetings | |
fileName: TKTK | |
openNote: true | |
``` | |
## Meeting Notes | |
```dataview | |
TABLE file.cday as Created, summary | |
FROM "Timestamps/Meetings" and -#MOC | |
SORT file.cday DESC | |
``` |
moshin34
commented
Jan 13, 2025
via email
I really like this meeting MOC concept. I am on a sales team and attend an absurd amount of calls. I'm afraid if I had a running list of meetings, like in this example, it would just turn into an infinite scroll. Any thoughts on that or strategies? Perhaps I'm looking at this from the wrong perspective. Thanks!
@chriscflowers Instead of making individual notes for calls, maybe organize all the notes by company? Then on each company note, have a section for each call, so you're not drowning in notes for each meeting.
Hi Dan, I'm new to Obsidian and been greatly appreciating your content. Quick question for you what does %% tags:: ... %% do?
@AlexandreBorowczyk nothing anymore, apparently. I think it was a relic of something I borrowed from someone else's template that isn't serving any fucntion that I can tell anymore. Good catch. Feel free to totally disregard.