Epic: CSV Download Feature

[bberhane]

Overview

We need to add an option to the website to allow people to download a spreadsheet of their selected data so that this information is accessible to them without them having to go online to retrieve it.

All Related Tickets

PM

• Create Use-Case Spreadsheet for NC Based on SR Type #1745

Design

• Add Export to Search and Filters Modal #1695

Dev

• New feature to allow end users to export 311 requests data to CSV using Map filters directly from the Map page #1586
• SR CSV download functionality needs an Address and Count export  #1746

Resources/Instructions

• Users should be able to download a spreadsheet of the highest incidences of request types
  • One spreadsheet for one request type: neighborhood council, request type, number of requests at a given address and time frame, one neighborhood council
  • Data that will be downloaded will only include one request type at a particular period of time
    • Spreadsheet will generate only the address + number of requests
• Provide users with some suggestions as to what to do with the data
  • e.g., making use of public services AKA bulky item pickup – let them know what the cost is for using it if any [This is what you can do with the data; this is one example (bulky items)]

[ryanfchase]

I'm feeling like this should be an Epic (e.g. data export feature) since I think each action item will end up being a sizable amount of work for a member of each team. Here are the tickets that would be attached to this epic:

• (modify existing Design ticket) add a download button + We'll need some messaging ... only one Request Type: there is a design ticket being worked on right now that will need the deliverables modified to match this ticket's requirements
• (suggested PM ticket) Come up with the suggestions about what to do with the data, Bonnie suggested we come up with a few, and the rest can be determined as a later effort
• (suggested Dev ticket) Implement the behavior of downloading the csv data in the format specified in this ticket. We can also reference a previous dev ticket that began the initial work of implementing the data export functionality

Feel free to leave a comment to discuss, otherwise happy to discuss this on Wednesday.

[bberhane]

@ryanfchase I thought the same thing when I was making it but was waiting for you to say something!

[ryanfchase]

@cottonchristopher instructions for converting this ticket to an epic:

• change title from Download CSV for a particular request type and time frame to Epic: CSV Download Feature
• remove labels: Role: Frontend, Size: Missing
• add labels: Epic, Size: epic
• Move Project Board card (from New Issue Approval to Epics)
• overview can remain the same
• remove all action items
• add the markdown below to start tracking PM tickets, dev tickets, and design tickets:

### All Related Tickets

#### PM
- TODO, create PM ticket: "Create suggestions on how NC can deal with service requests"

#### Design
- https://github.com/hackforla/311-data/issues/1695

#### Dev
- https://github.com/hackforla/311-data/issues/1586
- TODO, create Dev ticket: "CSV Download functionality should group by request type and display count"

• Resources/Instructions remain the same
• Finally, remove label draft