Explain the problem as you see it
The current system requires a somewhat tedious and memory-dependent process to locate specific nodes in the system. I often struggle to remember the exact spelling of the nodes (or the exact wording) I want to reference. This makes using the @ command to search for nodes difficult at times, as it requires precise spelling to return results. For example, to locate a specific node from my wishlist, I need to search using #wishlist and sort the results by date created. This is a task I find myself repeating on the homepage numerous times.
Why is this a problem for you?
This issue slows me down sometimes. I have attempted multiple workarounds, such as creating a default wishlist search, so I can quickly retrieve it using @wishlist. However, this challenge is persistent across different nodes with different tags. Also, I've tried @#wishlist
, which kind of works but it is not able to filter further, as it is quite randomly sorted, also it does not work when looking for particular child nodes under parent nodes that I can identify.
Suggest a solution
To address this issue, I propose the implementation of a Quick Search Command feature that allows users to find nodes quickly and efficiently, even if they do not remember the exact spelling. This could involve a command that allows me to make a fast search to narrow down the node. For instance, using natural language commands such as "Find node with #wishlist created last week" or "Find node tagged #chapter under parent node for #book". Or an alternative solution could be to refine the @
dropdown to make it easier to trawl through different filters.
This way, we can retrieve nodes in a more intuitive and efficient way, without needing to remember the precise spelling or where it is exactly located. It would streamline workflow and make for a more satisfying referencing experience.
1 Comment
Try using cmd+k on an empty node and then start typing exactly what you describe above. This pretty much already exists to an extent