Some thoughts about the black box of classification relationships

JSN

Just thinking out loud but more often than I would admit it happens that classifications develop a dynamic life on its own - especially when new things are in developement.
Sooner or later the quesion arises if the one or the other classification can be purged … organizing classification with the category folders is a way to better structure classifications, unfortunately there is still the renaming issue but at least there is a way to bring some order in the file.

So again, the cleaner the standard is set up the better, but it is also within the nature of project that the need for new classifications, rules, itos, … emerge and the more people are involved the more important it is to have a clean and self explaining file. To cut a long story short, renaming and removing classifications can ruin a lot without notifying the users.

Would it be possible to detect and visualize the relationships and dependencies between classifications and other classifications, rules, itos?
As a first step it would be great if there would be a warning or better the information if classifications are “in use” or if they are just for the solitary purpose of visualizing.
Spinning this further it would be awsome if you could also view or export some kind of graph for documentation and better understanding where all the logic can be grasped from one viewpoint, although this might be a bit ambitions I think usability would improve a lot.

Probably with the ongoing developements of Solibri X this can already be tracked better than today?

JSN

Things have changed to the better since this post was created, still some things remain in the dark.

Apart from a comprehensive summary to quickly see what is used where also small improvements would be a gift.

E.g. it would be more than great so see which cross referenced ressources are effected.

At least a tooltip would be much appreciated. Now it’s a bit hide and seek.

Moreover - those warnings are not showing if e.g. classifications are closed - why?

Additionally, exporting all Classifications and ITOs (once the link to a save location is broken ) one by one is a monkey job. Why is there edicated user friendly “Export all” functionality?

Ideally with the improved functionality that

Save Locations and Names of Classifications are stored - even if the link is broken.
Sava Names of ITOs can be different than titles …

And so on and so on …

JSN

Additionally, exporting all Classifications and ITOs (once the link to a save location is broken ) one by one is a monkey job. Why is there edicated user friendly “Export all” functionality?

I mean, there is not even a “Select all” option …

Nedlees to say that I have to select the path over and over again. And suddenly it just aborts because the OS does not allow me to save the classification names in the file system.

Leading me again to the old question why ressource save names are not saved and it is so hard to give them a different name in the consecutive workflow.

And if the process aborts, I have of course to select all the ticks again and again and again.
But the best part is - in the end there are some files even missing and I have to manually resave them anyhow.