Thanks for the link. I don’t know why, but I find some of the TC workflows to be less than user friendly. I’m not saying what they are doing is wrong, but it can feel like stepping into the unknown with an almost alien interface. Simplicity is crucial for successful software, if you need a manual to explain the process you are already loosing the battle.
For me S&I it would be a simple and quick way to set up Scenes or find things that are buried in the model for editing. Outliner is great and I use it a lot in preference to Tags but if you add new elements then hiding those new elements in multiple Scenes can become tedious if the Outliner tree isn’t structured. If you are familiar with the attributes in the model then the search workflow should be a simple case of creating a Rule with a few lines to search in “Attribute X” for the value of “My Setting”. Updating the model content in the scene is then just a case of reapplying the Rule.
I appreciate model data management is still on a learning curve, but I also think in the same way as some people don’t need cloud hosting, it should be possible to attach basic attributes in an SU model to assist in visibly breaking down the model & also documenting in LO.
I was thinking last night that this idea bears some correlation with the Diffusion interface, in that it could accept natural language to parse the required elements to display e.g. “Show me all the walls & doors on the second floor with a fire rating”. That’s possibly wishful thinking at this stage, but you get the idea.
EDIT: I have added to my posts in the IDK Compilation thread which may clarify my objective.