Add paging to full-width treeview for top-level records with more than 50 immediate children, to improve performance
|Target version:||Release 2.5.0|
|Google Code Legacy ID:||Tested version:|
When the full-width treeview is used and a large collection with many immediate children (i.e. many series below a collection, etc) is opened, the page takes a vary long time to load. The sidebar treeview opens much faster for the same collection, because it already has a sort of paging built in.
This feature will add paging to the full-width treeview for direct children of the top-level record. This will not affect lower level descendants - if you have a collection with a few series, but each series has thousands of file-level descendants, the pager will not appear. However, for cases where there are many direct child descendants of the top-level parent record, this can improve performance.
Implementation has been modeled off how paging was added to the hierarchy browser in feature #11955: when there are more than 50 child records from the top-level parent, AtoM will only display the first 49, and will present a button (top-right above the treeview) that includes a count of the remaining records. Clicking it will load the next 50 descendants, and provide a reset button to return the treeview to its initial load state prior to paging. Additionally, if there are still more records after the first page, the count will be updated and a button to load the next 50 will be available.
See the attached screenshots for more information. Also attaching a CSV for testing - copied from the Irving Steinberg Collection in AtoM's public demo site, but with the child records repeated so there are 108 children total.