Hello,
I’m working out how to do tasks in Emacs. Right now I was doing very trivial things: literally just writing down what I want to do today as a list in my daily note (I use org-roam), not even really keeping track of if something was done/undone. I’d just look over the lists of tasks for today at the end of the day, keep internal track of what must be moved over to tomorrow, and redo the whole thing again.
I’m thinking of moving to a (only mildly more complex) workflow. I’d still use my daily as a scratchpad for writing down everything, but the broader structure for tasks is as follows. I’ll keep everything in a top-level refile.org (outside org-roam), and have four states: POOL, TODAY, DONE, and CANC. All tasks by default go into the pool. Every day in the morning, I look through the POOL list, and move some tasks over to TODAY. Throughout the day, I just look at the TODAY tasks. By the end of the day, the TODAY tasks are either DONE, CANC, or left as-is. For any tasks which still stay TODAY on the next day, they go back to the pool. All DONE/CANC tasks get archived.
Does this seem like a reasonable workflow? I worry that the pool might grow significantly large, and the real blocker would be going through it each day in the morning-any suggestions for that? (perhaps I would just need to try things out for a week or two with this setup, and see how they work out.)
Concurrently, I want to do a CRM-like thing in org-roam. Specifically, I want to have a node for each person I know, keep track of their birthdays/etc in it, and note down any specific information that distinctly needs to be remembered. At the same time, I want to use my dailies as a log to keep track of my interactions with the person in question-so for instance, any time I have a slightly prolonged meeting with someone, I’d jot down a quick note about the meeting and what happened within it, linking to the person in question. A few questions about this:
- Having birthdays of people in their nodes would necessitate me pulling in my org-roam directory into the files that the agenda considers. I could probably filter by tag? maybe that would suffice.
- Pulling the org-roam directory in just for birthdays seems somewhat overkill. I could have a separate birthday.org file which I maintain outside org-roam, and keep track there. I don’t know if this is ideal though? have people tried playing with CRM-building with org-roam?