Couple basic questions on searching



  • Avatar
    a g capey

    Hi Robert,

    Not a solution, but comment.

    I can see the sense in what you suggest, but how would you ensure that you got the text right ? That is, to make sure you type in:Next Actions  not    in:NextActions .

    As an aside, I do most of my wfy work on a desktop, so have 3 browser windows open looking at wfy starred views - Home, Client1, Client 2. Given the speed of wfy I can search these views as quickly as composing a complex search string.

    As I said, just a comment.



  • Avatar
    Robert Talbert

    "how would you ensure that you got the text right ?"

    I don't know because I'm not a developer, but maybe it could work using quotes to match exact strings, like we currently do with searching, ie. In:"Next Actions".

    Re: the multi-tab setup, that's definitely a reasonable workaround, with the main cost being you have more stuff to keep track of on the desktop, also that doesn't translate to the mobile apps.

  • Avatar

    Short answer: there is no "in:" search operator equivalent. If you want to confine a search to a node, the only way is to zoom.

    Here are the available search operators:

    I use a GTD-ish system, and mitigate this search issue with format. Rather than use a Projects node, I use a #project tag, and I mix one time actions and projects under an "Area Of Focus". Then I zoom on the AoF, and search to get both. Also, I don't use a #next tag specifically, instead the act of adding my context tag implies "next".

    Area of Focus
    • One time action @context
    • Multiple Actions #project
      • This is the next action @context
      • This isn't next
    • Another one timer @context
    • Another #project
      • Next action @context
      • Not next

    You can also "save" searches by either starring them (and access them anywhere), or copying the link and pasting somewhere convenient.

  • Avatar
    Robert Talbert

    Thanks for that. Putting projects and single actions under the same heading was something I considered and may yet try out, although it's not "canonical" GTD (which says that actions and projects should be in separate lists). Another way around this I've considered is to keep Action Items and Projects in separate lists, and when I decide what the next action on a project is, just physically move it into the Action Items list. Then there's no search necessary, just focus in on the Action Items list. That's got it's own set of pros and cons. 

    One question about your setup -- do you actually literally use the word "context" in your @context tag or do you replace "context" with the name of the context like @work, @home, etc.? 

  • Avatar

    re: contexts
    the latter... fwiw, I keep a pretty stable list of five contexts

    re: "canonical"
    Oh my, don't get me started... 

    GTD was created 18 years ago as a tool-agnostic system.  Discrete "lists" can literally refer to an analog system... a piece of paper or a folder.  I see no reason to limit myself to these concepts in a digital system. My philosophy is design your system to match the strengths of your tool. Example: a WorkFlowy home search for my project tag is my "discrete" project list.  Another area where I'm not canonical, Waiting For.  In my system, this is just another context: @waiting.  The nice thing about WorkFlowy is you can design your own system... and don't have to force-fit your workflow into someone else's idea of what GTD is... including mine :) 

Please sign in to leave a comment.