Hi David,
Yes, the full-width treeview will definitely run into issues in its current format, when viewing larger hierarchies. If the hierarchy is large enough, it may fail to load at all. In this initial development, the full-width treeview is most suitable for small-to-medium sized hierarchies.
This is kind of a perfect example of our comunity-driven development model in action. The current implementation of the full-width treeview meets the needs of the client who sponsored it - they did not have the budget for further scalability testing and enhancements. Our user community has been asking about treeview enhancements in AtoM since our ICA-AtoM 1.2 release - you can see some of this in our historical wiki documentation,
here. This implementation meets many of the requirements that came out of those conversations, but there any many more improvements and enhancements that could be made. Our hope is that other users will help improve upon the full-width treeview in subsequent releases - adding scalability enhancements such as lazy loading or pagination, adding further functionality, adding configuration options (such as whether or not the identifier is displayed), etc. Since the initial development has already been sponsored by 2 institutions, we're hoping it will become easier for a broader set of institutions to contribute smaller but essential improvements. In this way, the new feature can become iteratively improved over time without one institution or individual having to shoulder the entire cost before anything is publicly available.
The regular treeview will still be available - there is a configuration option for choosing the treeview in the settings. So we encourage each user to test the full-width treeview across a wide variety of holdings, to check on the performance before enabling it on a production site. For those institutions excited about the full-width treeview but running into performance problems - we hope you might consider sponsoring enhancements, or submitting pull requests?
Note that we already have at least one client who has expressed active interest in this development - so I'm crossing my fingers that we'll see at least *some* scalability enhancements included in the 2.4 release.