Sharing an Item Within a Document, Not Entire Document

šŸŒŸFeatures
7

FILTER~SEARCH METHOD & RESULT / WORKING EXAMPLE (related to my above post)
Here I will try to illustrate what I think would be a typical application employing an outliner for project elements tracking, and the case for Exclusive ListElement Sharing (exclusive meaning sharing it wonā€™t lend full access to the host document for the sharee).

Disclaimer: I am not an ace at GTD or related methods. My organizational approach is still very much a work in progress. As well, other related List aspects are not on display here (InBox, etc). That said, Please feel free to comment on anything.

FRAMEWORK
**Main Doc: **

  • PrimeConcernDocument Sections (the main Dynalist Doc for this example)
    Primary Sections I-III
  • "People Keep 'em spinning": for daily/periodic tracking with agents
  • "People Tasks Tracking": for tracking tasks under explicit stewardship by specific entities
  • "Locales / Zones Tasksheets": for filling out and tracking explicit project zonesā€™ needs+conerns
    **ā€¦**and then they are all readily interlinked primarily using tags

Tags Setup

  • Tag Group A: TIME stuff, like #Now, #Today, #Later, etc
  • Tag Group B: TRADES/PEOPLE: @AdamA, @BarnyB, @ConnieC, @DPeople4 to ZPeople26, etc
  • Tag Group C: LOCALES: #ALocale1, #BLocale2, #CLocale3, #DLocale4, etc, (then there may be Zones as well)
  • Tag Group D: DISCIPLINES: #Glass, #Wood, #Steel, #Rock, #Cement, #SecurityItem1, #SecurityItem2, #ElectricalResource1, #ElectricalResource2, etc, etc
    (Note: Those tag formats are morphing with multi-prefix assignments, but Iā€™m not addressing that here.)

======================================
Example Filter~Search Criterion
Brief description of this ā€˜workingā€™ example filter: Iā€™m targetting a couple prime people working project aspects at 2 locales. One of the locales has 2 zones. Other people are involved in work at these locales. I want a quick overview of anything relevant to the two people/groups in question, with relation to #ALocale1, including anyone else tangentally engaged in job aspects with them there, AND I also then want a summary on #ALocale1 lists at the end.

======================================
The resulting list structure weā€™re after will resemble something like:
PrimaryConcernHavingManyProjects (doc)

  • People Keep 'em Spinin

    • @AdamA -call for things today
    • @BarneyB -call for things today

  • People Tasks Tracking

    • @AdamA
      • things to do
      • #ALocale1 things to do
    • @BarneyB
      • things to do
      • #ALocale1 things to do
    • @ConnieC
      • things to do per @AdamA or @BarneyB

  • Locales / Zones Tasksheets

    • #Alocale Tasklist
      • Stuff @AdamA is working on
      • Stuff @BarneyB is working on
      • Stuff being done elsewhere that is specifically related
        ======================

Filter~Search Looks kinda like: ancestor:#ALocale1 -ancestor:#BLocale2 -#BLocale2 OR #ALocale1 -ancestor:#BLocale2 -#BLocale2 OR ancestor:@AdamA -ancestor:#BLocale2 -#BLocale2 OR @AdamA -ancestor:#BLocale2 -#BLocale2 OR ancestor:@BarneyB -ancestor:#BLocale2 -#BLocale2 OR @BarneyB -ancestor:#BLocale2 -#BLocale2

NOTE: I have limited the search criteria in the example, which is intended to be illustrative, and which technically might should include consideration for excluding other Locales.

Filter Logic Explanation: Because Locales 1+2 have intertwined concerns, and with the people in question as well, I need to use some separation in the filter logic, soā€¦
::Get locale 1 stuff, i.e., anything tagged locale1 or with it as its ancestor, but minus the Locale2+ stuff:
ancestor:#ALocale1 -ancestor:#BLocale2 -#BLocale2
OR #ALocale1 -ancestor:#BLocale2 -#BLocale2
::Get group1 stuff, i.e., anything tagged group1 or with them as its ancestor, but minus focus on any of their work going on in Locale2:
OR ancestor:@AdamA -ancestor:#BLocale2 -#BLocale2
OR @AdamA -ancestor:#BLocale2 -#BLocale2
::Get group2 stuff, i.e., anything tagged group2 or with them as its ancestor, but (again) not focussing on any of their work going on in Locale2:
OR ancestor:@BarneyB -ancestor:#BLocale2 -#BLocale2
OR @BarneyB -ancestor:#BLocale2 -#BLocale2

Note1: Some #BLocale2+ stuff may still appear due to deep entanglements, but the focus will remain prominently on the desired objective -these two guys/gals/groups and Locale1

Note2: All references to an ItemX in this case include calls to both ancestor:ItemX and ItemX, but this is, obviously, not always the case. The ancestor feature in Dynalist provides flexibility in how one might employ ancestor vs individuated tagging -not uinder discussion here, but important to note.

========================================
Results -And so here we go. This is based on a realworld example, but with a totally ficitious framework.

=====================================
PrimeConcernDocument
. . note: I am not showing the whole document anywhere, only its conceptual structure map has been identified, and then this filter-result example.

  • I. PEOPLE KEEP 'EM SPINNING -DAILIES -TERSE LIST

    • Result: list limited to people in the filter call. I can immediately see whats on the front burner with the two people in question:
    • @AdamA- call per ruksor completion due in 1 week
      • sheā€™s gotta followup on the XY Frame layout first
      • (entry hidden) something to do with #BLocale2
      • sheā€™s flyin out to #CLocale3 on Wed (and this would be hidden as well if filtered same as #BLocale2)
    • @BarnyB- set plan shed on track4
      =====================================

  • II. PEOPLE TASKS TRACKING BREAKOUT

    • Result: list based on people and their work at Locale1 per the filter call, minus their tasks at Locale2 (except for incidental entanglements, so then will pull in other relevant people and locales where intersections exist [hence @ConnieC below]). Gives me a good overview from a ā€œworking-crews perspectiveā€, with focus on the relevant responsibilities of the primary people in the Filter-Query focus.
    • @AdamA (contractor) - ref on plan trak in proj2 book
    • -remove Carl off term p #ALocale1
      • followup on glassB frameW
      • [entry hidden] elect extension for R-term #BLocale2
      • needs to follow on new secsys co #CLocale3 [maybe hidden if #CLocale3 also filtered on]
      • (entry hidden) a description on thing to do with #BLocale2
      • another descrip per #CLocale3 in general [maybe hidden if #CLocale3 also filtered on]
    • @BarnyB (contractor) - set plan shed on track4
      • Get #Flocale6 #zoneX factor3 in order [maybe hidden if locale or zone filtered on]
      • start working plan for sub-section A, must review with @PersonZ (owner)
      • #ELocale5 replacements need substrate comp [maybe hidden if locale filtered on]
      • ask about the new *#zoneV [maybe hidden if zone filtered on]
    • @ConnieC (controller) - ::trak/report
      • #ALocale1 Bus and Auto+Sec System budget review
        =====================================

  • III. LOCALES / ZONES TASKS

    • Result: list based primarily on relevant Locale(s) in the filter call. So below the above trimmed down work-crew overview I then get here an overview of the relvant Locale(s) / Zone(s).
    • #ALocale1 (from the Filter Query)
      • #ZoneT
        • @AdamAand @BarnyB Access changes
            • more sub stuff
            • more sub stuff
        • @BarnyBand @DPeople4 meet routing when ADelta met
            • more sub stuff
            • more sub stuff
        • 2ndary storyboard on Elecy
            • Sub1 stuff
                • more sub stuff
            • Sub2 stuff
                • more sub stuff
      • #ZoneYY (another zone in ALocale1)
        • @ZPeople26 and @BarnyB Delta Bravo
            • more sub stuff
            • more sub stuff
        • @BarnyB and @XPeople24 conf post #DeltaB
            • some sub stuff
        • Transfer over to #ZoneB
            • Sub1 stuff
                • more sub stuff
            • Sub2 stuff
                • more sub stuff
    • #BLocale2+ [any jobsites without reference to one of the people on the filter will be suppressed, but if one of them has related work at an otherwise excluded site, that list item will be displayed
      • Send updated sitemap to @BarnyB
        • subnotes
      • [all other entries for site are hidden (not relevant)]

==================================
WITH EXPLICIT LISTITEM SHARING ONE COULD SEND AdamA or BarneyB A LIST RELEVANT ONLY TO THEIR WORK THAT AUTO UPDATES.

WITH EXPIRING LINKS, ONE COULD HAND OFF AUTHORITY TO SOMEONE ELSE, AND/OR RETIRE AUTHORITY ALTOGETHER (but right not you cannot change the link or access to it -big problem!)

##############
I hope this conceptual description and example are useful in providing prime insight into

  • how powerful Dynalist can be for quickly bringing focus onto a multiplicity of aspects of an explicitly extracted areas of a broad job/concern ā€¦that exists within a deeply diverse host-concern having many jobs. Andā€¦
  • how valuable a tool Dynalist can be for doing this, Andā€¦
  • how much greater value it would have if ExplicitListItem Sharing, as well as Expiring Links were onboarded (game changer).

Thank you for you interest.
Thank you Dynalist team for the inspiring project.
Twohawks

2 Likes