I believe JAndrews approach is still relevant. Also with smaller projects.
If you make notes on an ‘atomic’ scale–distilling a larger idea into smaller pieces–it does not matter what the size of the project at hand is.
You don’t need to ‘organise’ them.
Unless you want to. You could use concepts like “index notes”, “Maps of Content (MOC)” etc.
Let’s use a bit of imagination.
I imagine my Vault to be a forest. The trees are the notes. Every tree has also ‘directions’ to the location of other (relevant) trees.
When I need to answer homework questions, I walk towards the tree that is likely most relevant. (An index note could tell you to ‘start to walk here’.)
At the tree, I write down what I read and walk down the path laid out for me. (Shoulder pat for my past self!)
Once I have answered the question I repeat the process.
You can do the same with papers that you need to write. Walk up the first few trees, go down the path and see what comes out.
Once you discover new information plant a tree to a random location in the forest. It would be helpful if you put directions to other trees that might relate.
Slowly grow your forest in the process.
Main takeaways:
- Plant trees with the (atomic) knowledge you gather over time. No need to plant them in sections of the forest.
- I don’t always make ‘literature notes’ if the idea is described clean enough in the source material.
- Unless your forest is HUGE do you really need an index to find the first tree that you need? I just search for a relevant keyword in Obsidian. Or take a look at the graph view for something that catches my eye.
- There is no need to ‘put it under …’. They are your trees and your forest. Your personal knowledge. Add a source to keep track of where you got the info from. (For referencing it in a paper, for example.)
EDIT: Clearer sentences.