You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default listing of requests is by latest activity. This can be useful to browse "what's being requested now", and to see new information releases. For someone wanting to zoom out a little and look for themes across months or years, this format makes it difficult to navigate. The list is limited to 25 per page, and the "movement" as older requests get bumped, both make it difficult in this context.
We could offer a "browse by date" view, per authority, where you can see every request made in each year on a single page. We'd render only the basics (request title, status icon, and creation date) to create a really information-dense listing.
Depending on performance, we could either show all years on a single page (e.g /body/dfh/requests/calendar) or a page per year (/body/dfh/requests/2023).
Ideally we'd also be able to easily filter this down to only show successful (or partially successful) requests.
The text was updated successfully, but these errors were encountered:
The default listing of requests is by latest activity. This can be useful to browse "what's being requested now", and to see new information releases. For someone wanting to zoom out a little and look for themes across months or years, this format makes it difficult to navigate. The list is limited to 25 per page, and the "movement" as older requests get bumped, both make it difficult in this context.
We could offer a "browse by date" view, per authority, where you can see every request made in each year on a single page. We'd render only the basics (request title, status icon, and creation date) to create a really information-dense listing.
Depending on performance, we could either show all years on a single page (e.g
/body/dfh/requests/calendar
) or a page per year (/body/dfh/requests/2023
).Ideally we'd also be able to easily filter this down to only show successful (or partially successful) requests.
The text was updated successfully, but these errors were encountered: