Hierarchy browser Reset button missing if treeview pager limit not reached
|Target version:||Release 2.5.4|
|Google Code Legacy ID:||Tested version:|
In feature #11955 we added the hierarchy browser to AtoM - a full-width treeview that can be enabled by an administrator to browse the archival description holdings of an AtoM installation using a hierarchical treeview.
To help performance, a limit to the number of records loaded at once was added - typically limited to 50 records per load. If more records were available, then a count of remaining top-level descriptions is provided with the option to load more, as well as a "Reset" button, which will collapse all expanded nodes and return the hierarchy browser to its initial state. However, if initial load limit is never reached (for example, if there are only 40 top-level descriptions in an installation), then none of the buttons appear - including the "Reset button.
The "Reset" button is useful even when the initial load is never reached, since it allows a user to quickly collapse all expanded hierarchy browser nodes. This issue ticket will address that bug, ensuring that the "Reset" button is present regardless of whether the pager limit is reached or not.
- Visit an AtoM site with less than 50 top level descriptions, and make sure the hierarchy browser is enabled via Admin > Settings > Treeview
- Navigate to Browse > Archival descriptions and click on the Browse hierarchy button at the top of the results
No Reset button is available
The reset button should be available on the hierarchy browser page regardless of the number of records present.
#7 Updated by Dan Gillean about 2 years ago
- Assignee deleted (
- % Done changed from 0 to 100
The final functionality, compared to the current behavior, is such a minor change, and there are differences between the 2.6 and 2.5.4 functionality - so in the end, I've decided to leave this as is in the 2.5 documentation, and update the 2.6 documentation instead. In 2.5.4, the only real difference is that the reset button is not displaying in the screenshots, which should be fine for one point release out of 4 in 2.5, especially with 2.6 arriving soon.
Changes added to 2.6 docs in https://github.com/artefactual/atom-docs/commit/56ed038acf79fc22d41e6a23830572fd1e091306