I used that example due to the part of your earlier statement: āā¦some organized by topic, some organized by date, as a logā¦ā ā¦figuring searching by āsomedateā would be relevant to your inquiry.
I use the desktop app mostly. I did not realize not back arrows on the phone-app!
It seems you are correct about doc-root search, unless you use one of the other search methods, which only gives you either
- all docs, or
- flat results (not editable)
I have some really long joined OR statements, e.c. See:
https://talk.dynalist.io/t/please-consider-adding-ancestor-element-to-facilitate-simpler-deeper-searches/
SOME EXAMPLE SEARCHES:
ā¢ Example1: #NOW @Person1 OR #LocaleX #Today
(without any quotes) searches for anything tagged with NOW and Person1 tags, OR having tags LocaleX and Today
ā¢ Example2: Using the āancestorā operator. Logic Note: only direct parent is targetted.
@Person2 #NOW OR @Person2 #Today OR #Today ancestor:@Person2 OR #NOW ancestor:@Person2 OR @Person2 ancestor:#NOW OR @Person2 ancestor:#Today
ā¦will search all occurances of items tagged Person2 either containing Now or Today tags, OR with āchildrenā list items relevant to Person2 Now and Today tags, i.e., all variations.
ā¢ Example3: parent:@Person2
::any List where the Parent Item is tagged Person2
ā¢ Example4: parent:@Person2 #NOW OR parent:@Person2 #Today
ā¦Any List where the parent item is tagged Person2 and the children are tagged either NOW or Today
Searching isnāt just āsearchingā. I think of it as āfilteringā In many casesā¦ out of a huge mixed list of all sorts of things I can change the list presentation to only present a āviewportā of what I wish to focus on.
For instance: I have 10 properties with various contractors and employees, different projects going on all over, various resources for different things (water, power, communications, maintenance, building, planning, etc, etc), AND in different timeframesā¦
ā¦SO, I can see a full list organized by, say, properties, then jobs, then interspersed with people, things, and timeā¦
a filter with "ancestor:<this property> OR <thisproperty> (or even using <these properties>)
now hides all the other properties not currently under consideration. Then add/mix-in the next logic operator, say to do with communications, then say to do with a couple different companies/contractors, then say some timeframesā¦
ā¦NOW Iām looking at exactly what I need to focus on, and nothing that I donāt AND I can edit/update right there in the FILTERED RESULTS.
ā¦kind of thingā¦ I hope that makes sense.
Iām not saying this is a workflow/setup for you, or even that I am not still working on figuring out how to better handle it, but hopefully this provides some potential options to consider.