I went through this cleanup process a year or so ago. I figured it was time to clean out the fridge and remove that old stale and dried up dishes of peas and carrots that end in the back behind the beer and soda.
I spent hours deleting old build 1.0 and build 2.0 assets I haven't seen since TRS2004 or TRS2006. The process was difficult at first because I thought about the people that made the assets who haven't been around for many reasons just like looking at old papers as we clean out draws. The process got easier and easier, and I removed as I went along. I felt great having accomplished this difficult task. I wish the process was so easy.
I used a simple sort by build, along with an installed and not pay ware type filter. I then highlighted a bunch of content and checked for dependents. If there were no dependents, I deleted the assets.
This worked okay, but there's a problem. Instead of telling us which asset is a dependency of something else, it just tells us there are dependencies when viewing the results. This then required sifting the data again, meaning highlighting fewer assets at a time to reduce the amount until I found the one or two assets that had dependents of something else.
For me the process became too painful, and I gave up because the amount of work needed to remove these few assets I could remove wasn't worth the effort. If we had a filter, however, along with another column in Content Manager as I've suggested in the past that could indicate that something is a dependency, we could easily glean through and remove old stuff without going through multiple hoops, summersaults, and ropewalks to clean up old assets.
John
Trainz User Since: 12-2003
Trainz User ID: 124863
TRS2019/Trainz-PLUS: 114800
TRS22 Beta tester