Explain the problem as you see it
As workspaces grow, the number of supertags, fields, attachments grow. We need a simple way to keep track of these as well as simple way to see how many assets exist in the workspace.
Why is this a problem for you?
Creating some basic searches is time not well spent
Suggest a solution
A set of standard, built-in search nodes that could be added to a workspace. For example:
- all fields in the workspace
- all active (assigned) supertags
- all attachments (images, files, etc.)
Could be an option under workspace settings to add some or all of these canned searches. Of course we could configure to our own taste once added.
1 Comment
I seek to handle this through inheritance/extension. Some standard searches.
But yes, it would give Tana more "mainstream appeal" if it was even easier to add some searches to supertags.
Some standard ones or a wizard.
Side note: When working out searches for supertags, I also find it worthwhile to consider what "type" of node it is. Some of my types are:
Artifacts - "notes" or items to be "processed" and then archived. Tasks are a subset.
Structural - (they are "permanent" for my graph - part of the spine). Think "master documents". They may have notes directed at them also. For changing the content of them. (Or the structure, when I am system-building).
Hubs - they are longer-term objects (such as people, assets, projects, etc.). They may change status but are generally used for accumulating / processing the information from notes and tasks.
The purpose of, and benefits of searches are different for these types.