Home

Requirements for the NSF 311 Web Application

High-Priority Requirements

1. [high-priority] Understand and refine the code structure -- make sure to check with Julia before making major changes [In progress]
2. [high-priority] Fix the sidebar while being able to explore the map [In progress]
3. [high-priority] Resolve the styling issue in the dynamic graphs (e.g., label margin, x-axix ticks, etc.) [Complete]
4. [high-priority] Data zoom-in and zoom-out functionality in the graph [In progress]
5. [high-priority] Fix the map view and Zoom range, so the users don't go outside of the map view [In progress]
6. [high-priority] Make the legend dynamic (currently, fixed number of classifications of color) [not started]
7. [high-priority] change "Subject" names from departments to the topic/type of reports generated [In progress]
8. [high-priority] refer back to https://betablocks.city/discover opening to better explain the reason/purpose of the tool and how to use it

8.1 Explain that this is a proof of concept of how information desserts manifest and how they relate to certain variables

8.2 Goal of the tool is the user (whoever it is) is able to identify different characteristics of information desserts by looking at these variable relationships

8.3 information desert for govt employees not getting reports/information of certain areas

8.4 want to show what effects what, want to demonstrate indicators which related to information deserts and other direct outcomes within neighborhoods/residents

9. [high-priority] make default setting to then show an interesting utilization for the tool, then have an advance-user option to be able to toggle/unselect certain variables
10. [high-priority] create a default setting for when presenting as a proof of concept ("All Subjects" + "Total number of reports" → independent variables can be "Poverty Index" (or Mobility?) to see
11. [high-priority] define/explain what we were looking at here by using this tool (with the default setting: a possible relationship b/w the variables to then see where the high poverty areas have low reporting); mention that single users are not included in this data; define/explain what do you mean by neighborhood (zipcode? hexagons? etc.)
12. [high-priority] explain the tool aims to demonstrate indicators that relate to information deserts and other direct outcomes within neighborhoods/residents
13. [high-priority] adjust "Subject" to be the topic/report type instead of the department (have subcategories where what is included in the topics)
14. [high-priority] scope down the "Color coded by" and "Dependent" variables to those that would be most interesting to look at and make them human-readable
15. [high-priority] label the neighborhoods, landmarks, etc for those not familiar with these areas on the physical map
16. [high-priority] not clear what "frequency," "all," and "heavy" mean, so make that more clear
17. [high-priority] include units on the black key for the map located on the bottom left of the screen
18. [high-priority] refrain from utilizing acronyms
19. [high-priority] make colors of the regression graph different from the blue ones used on the map page
20. [high-priority] clarify what “Non-Government" and "Unsure," utilize human-readable terms
21. [high-priority] different colors of the regression graph different from the blue ones used on the map page

Mid-Priority Requirements

1. [mid-priority] make the drop-down menu items dynamically load variables from DB.

...to be added more when the design requirements are generated.