-
org-ql
A searching tool for Org-mode, including custom query languages, commands, saved searches and agenda-like views, etc.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
If that doesn't work maybe you could use org-transclude to copy the todos around, though that would probably a bit more manual than what you'd really like.
Yes, this can all easily be achieved with the agenda. You can use one or multiple files to build a specific agenda view - I currently just use one. You can add a priority property to each todo (default A, B, or C - I add a fourth D and apply the Eisenhower matrix methodology when assigning a priority), add an effort property (whose value is an estimate or based on past experience) to each todo which could then be used to decide on what to work on based on mood, energy levels (e.g. it’s nearing the end of the day I’m tired what todo can I do in my last 20 mins), the time of day it is (e.g. I have 15 mins before I go for lunch what todo can I do in that time). You can add a context property to each todo to indicate when/where you can complete a specific todo - I use a tag prepended by an “@“ symbol e.g. “@work”, “@home” or “@other”). Your agenda can then be filtered (e.g. show me only priority A todos etc.) or sorted (e.g. show scheduled/deadline todos at the top of my agenda view, priority A next etc.) based on such properties. This can all be achieved with stock Org but you may be interested by packages such as alphapapa/org-ql, alphapapa/org-super-agenda which offer more flexibility/tighter control of what look you might want to achieve.
Yes, this can all easily be achieved with the agenda. You can use one or multiple files to build a specific agenda view - I currently just use one. You can add a priority property to each todo (default A, B, or C - I add a fourth D and apply the Eisenhower matrix methodology when assigning a priority), add an effort property (whose value is an estimate or based on past experience) to each todo which could then be used to decide on what to work on based on mood, energy levels (e.g. it’s nearing the end of the day I’m tired what todo can I do in my last 20 mins), the time of day it is (e.g. I have 15 mins before I go for lunch what todo can I do in that time). You can add a context property to each todo to indicate when/where you can complete a specific todo - I use a tag prepended by an “@“ symbol e.g. “@work”, “@home” or “@other”). Your agenda can then be filtered (e.g. show me only priority A todos etc.) or sorted (e.g. show scheduled/deadline todos at the top of my agenda view, priority A next etc.) based on such properties. This can all be achieved with stock Org but you may be interested by packages such as alphapapa/org-ql, alphapapa/org-super-agenda which offer more flexibility/tighter control of what look you might want to achieve.
I based it off of a comment I found on reddit (who explained their setup) and based it on this repository. It is automatic, so at every new month, a new file is created "2021-aug.org", "2021-sep.org", etc. I agree that its a nice time unit! Weekly is too much, and once a month is enough to evaluate if something is keeping around, or can be let go. (And plus, I'm never actually losing anything since it stays in the "older" org file).