Add is:mirror search operator

Planned

Comments

5 comments

  • Avatar
    Frank (Workflowy Support)

    Hi Charlie,

    We do have an "is:mirror" operator on our wish list :-)

    Fantastic workflow you've described!

     

     

    3
    Comment actions Permalink
  • Avatar
    HarryPotter

    -is:mirror is more important than is:mirror in my case

     

    this is the same for me as well

     

    when i'm searching the document, i don't want all the mirror nodes to show up in the search but only THE ORIGINAL

     

    e.g. if i search #task -is:mirror 

     

    right now i see every mirror node throughout the whole document which is redundant

     

    what i would love to see is the ORIGINAL mirror node only, along with all other nodes tagged as #task

     

    thank you

    2
    Comment actions Permalink
  • Avatar
    Max Yakin Bozek

    The problem with your request and the current state of the situation is that now there is no more "original node" with many mirrors. Rather, all mirrors are equal now; then… all of them are mirrors and "originals", as well. No way to conceptually distinguish them anymore, this new approach was a solution to deleting originals without deleting its mirrors.

    0
    Comment actions Permalink
  • Avatar
    Dominic

    I want to voice my agreement with Charlie.  I just started using WorkFlowy today, and my intention is to mirror all my tasks (organized by project) into my to-do list (organized by timeframe - this week, next week, later).

    I can envision a time when I have added many tasks, but forgot to mirror some to the to-do organization, so being able to search for "not mirror" would be very helpful to find those.

    A couple more details I would like to add:

    1) I assume most of my tasks will be at the lowest level of the bullet hierarchy, so it would be nice to be able to filter for that too.  For example, if I have a project name bullet, with a bunch of tasks underneath, each task should be mirrored, but not the project name.  It would be nice to avoid cluttering up the search result by filtering out bullets that are not at the lowest level, even if they're not mirrors...

    2) Similarly, there may be some nodes that I don't care to have mirrored to the to-do organization (perhaps a long-term personal project), so it would again be great to be able to filter the search to exclude items below any particular bullet hierarchy.

    Both of these details "mirror" (pun intended) Charlie's request for more powerful search syntax in general.  Of course, as I said, this is my first day with WorkFlowy so my apologies if some of these capabilities already exist and I'm just not aware yet.

    Thanks!  I'm really enjoying the tool so far!

    2
    Comment actions Permalink
  • Avatar
    Max Yakin Bozek

    Viewing Node Locations

    The Locations tab identifies all locations of a selected node in a hierarchy viewpoint. Multiple locations for the same node can be visualized together and you can navigate to any location where a node exists. Locations are grouped by parent and can be viewed in a collapsed or expanded format. Property values for each location can be displayed to determine similarities or differences across locations.

    For shared nodes that exist in multiple locations in a hierarchy viewpoint, the Locations tab provides an easy way to:

    • Identify all of the locations - including the full ancestry of the node

    • Navigate to any of the locations to browse or modify data

    • Visually compare properties for the node in different locations

      Note:

      The properties that display in the Locations tab are configured in the viewpoint inspector. For more information, see Configuring Locations Tab Properties.

    Tip:

    Even if a node doesn't exist in multiple locations, the Locations tab provides a list of ancestors for the node. Expand the ancestry list to navigate to any of the node's ancestors.

    To view node locations:

    1. Open a view and select a hierarchy viewpoint.

    2. Expand a hierarchy and select a node.

    3. Click the Locations tab.



    4. Do any of the following to navigate in the Locations tab:
      • Click the expand button to see the node's ancestry.

      • In the expanded view, click any of the node's ancestors to navigate to that node.

      • Click the navigate button to go to a different location of the node in the viewpoint.

      Note:

      In the collapsed view, you can navigate to the node only. You cannot navigate to a node's ancestor from the collapsed view. In the expanded view, you can navigate to the node or you can navigate directly to an ancestor of the node.

      source: https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/dmcaa/viewing_node_locations_100x257c7867.html

    0
    Comment actions Permalink

Please sign in to leave a comment.