...
Continuous scroll is problematic for accessibility and keyword searching across the collection. There are two continuous scroll areas in the same area. There has been an ongoing bug about some finding aids stopping loading the entire finding aid. Some people has describing the scrolling view as “nauseating.”
There are Jira tickets because repositories want some or all data fields for archival objects visible in the finding aid view, similar to scrolling through the PDF export. Having to click on each archival object is not acceptable (is it? Or should the repository manager be able to set up a default of certain fields that should display but not all fields?)
The collection tree (currently on the right side) tends to be a preferable “clean” view. A lot of users (documented in a couple of Jira tickets) want to expand and pull over the collection tree. This could be because the view might seem more “clean”
For extremely long finding aids, the combination of the finding aid view and collection organization tree is not helpful because both are buried in the middle of very long series, essentially duplicating the view while also not preserving orientation within the hierarchy. At least in the tree view, it should always be possible to see what collection, what series, you are in. (Should all series be visible, only the series “above” the current location” or only the most immediate series?)
The style sheet for the collection organization tab is problematic (hence possibly why people want to view the tree instead). There are three different font sizes, which might make it more difficult to see.
| View file | ||
|---|---|---|
|
Discussion topics
...
Time
...
Item
...
Presenter
...
Tickets | Notes |
|---|---|