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
Delivery Needed Map (DNM) only has a map view right now. This was intended to augment the slack app requests so volunteers can browse for open requests by location.
It would be better to also have a table view of requests so volunteers can do all the browsing on the DNM page. The popovers only show minimal information (first name, x-streets and request code).
They still have to sign up for the request on Slack, but hopefully this makes less back and forth.
Considerations
I don't have designs yet, but if you are up for it, you can draft something up
Hovering/clicking on marker on the map should highlight the table/list entry somehow. And vice versa. Kind of like how the yelp map view works.
Add ability to filter and search could be a second iteration feature.
We average about 30-50 requests so there is no pagination at the moment. Might wanna consider what might happen if we have more requests.
The text was updated successfully, but these errors were encountered:
I have a bigger ask that would be SUPER useful. would it be possible to sort open requests by time since the slack post? (and also display the lapsed time)
The message ts field which is used as a thread ID is also a Unix timestamp (https://www.unixtimestamp.com/index.php), so there wouldn't need to be any extra network calls
What
Add a table/list view of requests to https://crownheightsma.herokuapp.com/delivery-needed with the same information available on Slack.
Why
Delivery Needed Map (DNM) only has a map view right now. This was intended to augment the slack app requests so volunteers can browse for open requests by location.
It would be better to also have a table view of requests so volunteers can do all the browsing on the DNM page. The popovers only show minimal information (first name, x-streets and request code).
They still have to sign up for the request on Slack, but hopefully this makes less back and forth.
Considerations
The text was updated successfully, but these errors were encountered: