How do I create a simple dashboard / index file for tracking notes?
One of the problem I have is I take alot of notes and then they sit there. As per my understanding org roam does not have any guideline or suggestion for notes synthesis/processing.
I have the “index” tag and give it to a handful of notes; each with a title as a topic: e.g. “Emacs”, “Note-taking”, etc. When I create a note file, I insert one or more links to these index files, so that each index file has backlinks to notes related to the topic. I also show the number of backlinks in org-roam-node-find. If I filter the list by “#index”, I can see a list of all the topics and the number of notes for each topic.
Thank you for taking time to reply.
How do you track stages of note e.g. fleeting, fern , evergreen note? My goal is to publish more often. Ideally I want an index page with sub-trees representing stages “working” “public”, but I want it be dynamic (I don’t want to manually move notes among tree or update tags).
Over the years I have used emacs but never tried to learn lisp, but recently I read up on lindy effect, I realized I should invest in tools that would be there in the long term. If you have any advice/ideas/ I would appreciate them.
I installed the package.However I am not able to figure out the intended workflow.
If you use this package personally, do you mind sharing your config?
Another possible approach is “abusing” the very rich to do ecosystem in Org mode for this.
If you add fleeting, fern, evergreen and any other category that interests you in your org todo items, you can then make your notes have these states. Changing them is trivial, org-todo allows for time tracking, scheduling and much more.
Furthermore, you can add the todo state to your org-roam UI so you can search for the various states in org-roam-node-find. And you can also add these to your org-agenda and view them in such a menu which can be useful.
Its by no means the intended use of todos, but due to the extensibility of everything in Emacs, you can sorta repurpose it for this purpose, which you might find useful.
Can also provide some code for you when I have time, if this sounds interesting.