Explain the problem as you see it
Say you're on a class/meeting and you have a node zoomed-in to register what you're learning.
But what you're learning is related to a topic for which you have a node already in your library. So you reference that in the class/meeting node, expand it and start adding notes there.
Then you tag what you wrote as "#to revisit". You would probably want the fields of that node to be initialized with content from the class/meeting you're in, not only with content from the parent topic itself.
Why is this a problem for you?
This is a workflow I go through constantly, and would like it to be more fluid. Currently it's all solved by writing the fields manually, but we all know how that breaks the flow.
Suggest a solution
Add an option to initialize a field with content from the context (the currently zoomed-in page).
(While we're at it, why don't allow us to enable and prioritized the multiple initialization methods? - I know, I know, I'm just being lazy avoiding to write another idea page)
1 Comment
Very good point!