4 ms·
An important part of my workflow[1] is similar to this approach. I believe it's got a lot of potential if done right. One concern I have is the lack of file upl
by bachmeier 5y ago
An important part of my workflow[1] is similar to this approach. I believe it's got a lot of potential if done right. One concern I have is the lack of file upload support (I only see images) and that querying relies heavily on tags. WRT the latter, it didn't work until I was able to create new projects that only held notes related to a specific project/topic. The current trend of dumping everything into one big database and hoping for the best when it comes to review and retrieval just does not work for me.
[1] Based on what I can tell from the linked page, which doesn't give a ton of detail.
- losfair 5y agoFile upload is indeed a useful feature! Added to my todo list. On the second concern, nested tags are supported so you can have something like #project1/tag1, #project1/tag2, #project2/tag1 etc. - does this work for you?
- bachmeier 5y agoI personally don't care for nested tags. It's too cluttered, because even if focus on tags starting with project2, there's a lot of verbosity. What I do is analogous to a "working directory" where everything is relative to that directory. For instance, rather than #project1/tag2, if I click on #project1, the project1/ is prepended to all the tags automatically inside storage but hidden in the display of notes. Implementation is simple. If using Javascript, store the current project name in a variable and prepend it when relevant. Edit: Another advantage of this is that cross-project tagging stands out because the full tag is displayed.