National Day of Civic Hacking, September 23rd, 2017
This repository is for hackathon projects supporting the DC Department of Health.
Orkin Pest Control recently named Washington DC the third "rattiest" city in America, and long-time DC residents know that rodent populations have been on the rise. Mayor Bowser announced a "Rat Riddance" initiative last year, which aims to reduce rodent populations through changes in commercial practice and community awareness campaigns. In support of these efforts, the DC Office of the Chief Technology Officer (OCTO) has been analyzing 311 service request data related to rodent abatement requests and developing models to predict upticks in rat-related complaints in space and time.
The goals for our project are 2-fold:
- Develop models that can predict long-term trends in rodent complaints. These models will be complementary to ongoing OCTO efforts.
- Build out features on a public-facing 311 data portal that allows users to examine trends in service complaints over time and in their neighborhoods. This data portal will encompass all nuisance-related service complains, not just those related to rodents.
Food establishments that sell or serve food to the public must apply for a health permit and be inspected for compliance with the DC Department of Health. These establishments include restaurants, school cafeterias, bakeries, mobile food vendors, and markets. The majority of the permitted food service establishments in Washington, DC receive two routine unannounced food safety inspections per year. DOH follows the federal food code and only closes an establishment for critical violations that cannot be corrected while an inspector is onsite (for several hours) and poses immediate harm to residents and visitors to the District. The purpose of a food safety inspection is to ensure the food is being handled properly from preparation through serving. DOH seeks understanding as to whether or not there are common factors of establishments that can guide future training efforts for business owners and staff or that may help the department allocate staff resources in a more efficient and effective manner. Note that the number of times annually that a food retail location is inspected is based on its risk category.Any problems observed are recorded on the inspection report and the manager is taught the correct procedure or method immediately
The goals for our project
- Data analysis/visualizations of the DOH restaurant inspection data report
- Develop a model featuring relationships between location, risk category, serious food-safety violations, closure etc.
- Develop an application for DOH staff that tracks upcoming inspections, displays information on expiring licenses, and aids in the efficient prioritization of follow-up inspections.
- Add your name to our sign up sheet in the "Sign up sheet" tab
- Find an available task under Github Issues, assign yourself or your group to the task, and get hacking! We will be adding new issues throughout the day, so check back later if you don't see something that immediately catches your interest.
- Don't feel limited to the tasks on GitHub! If you have an idea that isn't listed, add your task to the "Tasks for Day-of" tab in the sign up sheet or come find one of us to chat about it!
We are recruiting individuals for the following types of tasks:
- Data cleaning: Help us convert raw data frames into clean feature datasets that are ready to integrate into models!
- Data visualization: Look at the available datasets (See the "Dataset summary" tab in our sign up sheet, chat with DC DOH agency representatives about maps and visualizations of interest, and create the visualizations!
- User interface/experience (UI/UX):
- Build out features for our existing 311 data portal in R Shiny (http://dc311portal.codefordc.org/)
- Design and start to develop a web application for the public to view DOH inspection reports for food retail establishments
- Design and start to develop an application for DOH staff that tracks upcoming inspections, displays information on expiring licenses, and aids in the efficient prioritization of follow-up inspections.
- Project management: Interested in helping us manage the project? Chat with one of the project leads!
- Start by forking this repository to your Github account (click "Fork" in the top right). Then clone the forked version of the repository to your computer using the URL listed under "Clone or Download".
$ git clone <url-of-your-fork>
- We use a triangular workflow - you should push to your Github account's fork, but fetch/pull from this master repository. Setting this up requires adding a remote to this repository account. "Git clone" will have created your repository in a new folder called "dc_doh_hackathon". Use these commands to add the remote to that new folder:
$ cd dc_doh_hackathon
$ git remote add dohhackathon https://github.com/jasonasher/dc_doh_hackathon.git
$ git remote -v
#you should see this:
dohhackathon https://github.com/jasonasher/dc_doh_hackathon.git (fetch)
dohhackathon https://github.com/jasonasher/dc_doh_hackathon.git (push)
origin <your/forked/url> (push)
origin <your/forked/url> (fetch)
- Commit and push your code to your forked repository with the following commands:
$ git add <your_filename> # adds the filename for tracking in your Git repository
$ git commit # a text editing software will popup and you can add a commit message there
$ git push origin master # push your commit from Git to Github
- Now, submit a pull request to merge your commit to the "jasonasher/dc_doh_hackathon" repository. To do this, go to the main repository. Navigate to the "pull requests" tab and click on the button "New pull request." Click on the link to "compare across forks." The base fork and base should say "jasonasher/dc_doh_hackathon" and "master", respectively. Change the head fork and base to "your-user-name/dc_doh_hackathon" and "master", respectively. Create the pull request, submit a comment about your commit, and you're done!
N.B., For future commits with your remote setup, instead of git push and git pull, use these:
$ git push origin <branch-name> #pushes to your forked repo
$ git pull dohhackathon <branch-name> #fetches and merges from the dohhackathon repo
Here’s more information on setting up triangular workflows (scroll to “Improved support…”).
Never worked with a triangular workflow before? Ask a project lead for help.
Rat Riddance:
The Rat Hack meets regularly at Code for DC meetup events. To stay involved after the hackathon:
- Join the Code for DC group on Meetup
- Join the Code for DC Slack and hop on to the #rats channel
- Check out our primary project page
- Make sure your name and contact information are on our hackathon sign up sheet!
Food Safety/Restaurant Inspections:
The restaurant insepction Hack meets regularly at Code for DC meetup events. To stay involved after the hackathon:
- Join the Code for DC group on Meetup and
- Subscribe for #restaurant_inspection channel
- Make sure your name and contact information are on our hackathon sign up sheet!
Rat Riddance: Jason Asher ([email protected]) and Elizabeth Lee ([email protected])
Restaurant Inspections: Mohammed Kemal ([email protected]) and Astrid Atienza ([email protected])