Use cases that could justify local data sorting and filtering

The present architecture puts the work of ordering and selecting records on the API. This is appropriate when the request frequency and payload is a factor in performance.
- Reducing the size of the returned data can positively aid performance
- Reducing the complexity (e.g. flattening) of the returned payload can remove the need for pre-render processing

However, there are cases with speed and flexibility and quality of UX can potentially justify local object storage (e.g. arrays).

1 - A session list that needs to paginate based on day or team
2 - Ability to reverse sort-order
3- Ability to switch to a different sort key in a given view (e.g. team name, coach name, date)
4- Ability to filter on region, coach, or student
5- Ability to display summaries like record-counts on any field, for a variety of dashboard/metrics