July 2019 Agenda - hackforla/311-data GitHub Wiki
Team Roll Call
Running Roll Call:Date: 07-30-19
Agenda:
- Roll Call
- Review Slides for meeting
- Conduct meeting
- Review meeting notes
- Plan for next steps
Notes:
Next Steps:
Talk Tech! 2nd Meeting on Tues, Sept 24th
- Get list of NC Regions from Empower
- Present Prototypes
- Presentation of Educational Material (NC)
- Presentation of Existing Visualization Tools
Date: 07-23-19
Agenda:
- Officially establish roles and team lead/representative
- Fill out Team Roster
- Continue outline of NC Member meeting agenda for July 30th
- Split up who says what and presentation slides/demo (if necessary)
- Review write-ups of prototypes for voting/final sign off
- Review comparison criteria section of Market Analysis report
- Review NC survey results
- Consider generating visualizations of survey results to share with NC members
-
Prototype or mock-up Diff Dashboard/Initiative ROI/ROII example for NC meetingprototypes - Finish card for web side
- Create follow up list of people that didn't fill out the survey
- and those who did?
Notes:
NC Meeting Attendees (a/o 7/23/19 @ 8:30p)
Attending
H4LA
- Bonnie ([email protected])
- Nina Kin [email protected]
- Lauren Sandberg [email protected]
- Roberta DePoppe [email protected]
- Joshua Marx [email protected]
- Russell Tan [email protected]
NC
- Albert Farias [email protected] - Filled Out
- Victoria Krauss [email protected] - Filled Out
- Brandon Walker [email protected] - Did Not Fill
- Gibson Nyambura [email protected] - Did Not Fill
- Obiamaka Ude [email protected] - Did Not Fill
- Kimberly Mitchell [email protected] - Filled Out
- Tamura Fatheree [email protected] - Did Not Fill
Declined
H4LA
NC
- Thomas DeVoss [email protected] - Filled Out
Waiting
H4LA
- Kevin Chrzanowski [email protected]
- Lexie Ulven [email protected]
- Armett Johnson [email protected]
- Rose Pender [email protected]
- Laura Kim [email protected]
NC
- Brian Carroll [email protected] - Did Not Fill
- Julien Antelin [email protected] - Did Not Fill
- Odalis Guevara [email protected] - Did Not Fill
- Nolan Moore [email protected] - Did Not Fill
- Clint Birdsong [email protected] - Did Not Fill
- Kelvin Guevara [email protected] - Did Not Fill
Next Steps:
- Prototype or mock-up Diff Dashboard/Initiative ROI/ROII example for NC meeting
Date: 07-16-19
Agenda:
- Review email that went out to NC Members
- Fill out Team Roster
- Review github documentation
- wiki
- readmes
- Overview of github administration items
- Review market-analysis report (Overview of what's already there)
- What's out there
- How are other people using these?
- Prevent hours of explaining what's out there
- Begin outline of NC Member meeting agenda for July 30th
- Create brief write-ups of prototypes for voting/final sign off
Notes:
- Drafted detailed outline for NC Member meeting agenda
- Room, projector, etc. are all reserved for NC Member meeting
- Decided to remove the Gov Correlations prototype idea at this point
- Agreed to move forward with the Diff Dashboard (primary goal) and Initiative ROI/ROII (stretch goal) prototypes
Next Steps:
- Kevin to fill out comparison criteria section of Market Analysis report
- Review agenda outline a final time before July 30th meeting, determine who is doing/saying what
- Review NC survey results
- Consider generating visualizations of survey results to share with NC members
- Prototype or mock-up Diff Dashboard/Initiative ROI/ROII example for NC meeting
Date: 07-09-19
Agenda:
- Establish who needs admin access to github
- DELIVERABLE Draft email for NC people about 311 data meeting (last Tues of the month)
- What is CodeForAmerica very brief
- What is Hackforla very brief
- Get them excited for the meeting
- Imagine the possibilities with 311 data at your fingertips
- Overview of the meeting and whats to be covered
- Brief on the questions that we have
- Mention cookies to encourage attendance
- DELIVERABLE Draft Google survey Q's -> Bonnie will create actual survey
- Do you know about 311 data
- Do you use 311 data
- Are you a member of leadership or a regular councilmember?
Notes:
- Link to deliverables: https://docs.google.com/document/d/12JQ46SVsyywmdwEFPpE-Q1xFHdXNIP-AnbSaPKs0Kvk/edit#heading=h.k0arncwly1xs
- Link to survey: https://docs.google.com/forms/d/1N_cY23y4u04oHOlkyQId-K3k11J23lUGwMljmNHpmMk/edit
Next Steps:
- Create github admin snazzyness
- Create brief write-ups of prototypes for voting/final sign off
- Create a market-analysis report (Overview of what's already there)
- What's out there
- How are other people using these?
- Prevent hours of explaining what's out there
- Clean up documentation
- Utilize githubs tooling
Date: 07-02-19
Agenda:
- Goals
- Continue brainstorming and thinking about what we might be able to do with the data
- Determine what frameworks we'd like to use
- Prototype
- Machine learning model
- Explore correlations prototype
- Russell
- Explore YoY MoM WoW diffing prototype on particular columns
Notes:
- Our knowledge base…
- Spark is the easiest machine learning framework (from Python)
- JavaScript
- D3 for visualization
- Colaboratory
- Free tool for python collaboration
- https://colab.research.google.com/
- Department of Transportation update re: 311
- Adding data on calls re: scooters!
- All scooter operators must comply
- You can now report on all kinds of stuff - where they're parked, multiple people on a single scooter, etc.
- MDS - Mobility Data Specification
- Adding data on calls re: scooters!
- Open Questions:
- Success Metrics…
- Are we counting number of calls vs. number of actual incidents? (i.e. what if multiple people call about the same issue?)
- Issue created date vs. closed date (time to close)?
- Success Metrics…
Next Steps:
- Overview of prototype findings
- Continue hacking on prototypes
- Continue brainstorming