📢: See this page with a table of contents at https://codeforphilly.github.io/datahack2020/.
💬: Be sure to join the #data-hack-chat channel of Code for Philly’s Slack.
Code for Philly, DataPhilly, R Ladies Philly, the Philly Data Jawn, Health Federation of Philadelphia, Prevention Point, the City of Philadelphia are hosting a data science hackathon to answer pertinent questions around the Opioid Crisis in Philadelphia. The goals of this event are to provide health organizations with insights that may normally be unavailable to them and to create analyses that help inform the public about the opioid epidemic in our city.
Hackathon planners have been working with our partners to identify and clean relevant datasets that would be helpful in answering these broader questions:
Feb 7, 2020 (Friday): Partner presentation night - Hack participants will have the opportunity to hear directly from partner organizations about the challenges they face and what analyses would be most useful to them. After the talks, participants will be encouraged to sign up to a team via this Google Doc.
Feb 8, 2020 (Saturday): First hack day - No formal presentations scheduled on this day. Upon arriving, participants will be encouraged to sign up to a team if they have not already done so the previous evening. Teams will then get together to discuss ideas for research questions to pursue, and work out any team logistics (including selecting a team leader, frequency of meetings, location of meetings, tools to be used, and roles in the team). Space will be available for teams to get started on exploring the data and familiarize themselves with the research topics and tools.
Every Tuesday, Feb 11 - March 10, 2020: Hack Nights - Space and pizza will be provided for participants to get together in person and work on the project. There is no attendance requirement, but everyone is welcome. Teams are also welcome to get together at other locations and at other times, but will need to organize these meetings themselves. Teams are also welcome to consider remote work options.
March 3, 2020: Wrap up analyses and start writing up report and presentation - By this point, teams should be concluding their analyses and should begin drafting their reports for partners. Teams should expect going through several iterations of these reports, and should therefore allow ample time before the final presentation night to make edits, tweaks and corrections.
March 17, 2020 (Tuesday): Presentation night - Teams will present their findings in front of their fellow hack participants, partner representatives and other data enthusiasts from the general public. Teams should decide on their own the presenter responsibilities, but all presentations are expected to be no longer than 7 minutes long and follow a predefined structure. Teams will have the option to make minor changes to their reports based on discussion at this event.
March 24, 2020: Final reports due on GitHub.
Each team is expected to submit a final report, that will follow the structure below (view an example):
This section should have up to 5 bullet points summarizing the main conclusions from the analysis. These should be worded in such a way that stakeholders without data expertise can easily understand what actios would be beneficial. It can be a shorter version of the conclusions section below.
*This section should list the names and 1-2 sentence descriptions of everyone who worked on the submission. E.g. “Party Parrot is a data scientist with Philly’s DataForGood nonprofit, and a student of applied statistics at Drexel. In both roles, she enjoys conducting predictive analyses and natural language processing.* #### Problem definition and dataset
This section should summarize the question your group has worked on, as well as any working definitions that you used (beyond what was outlined in the general description). Additionally, this section should contain any issues or challenges that you noticed in the data, that may be relevant.
You may structure this section in any way that makes results easier to understand and describe.
This section should have a bulletpoint list of what conclusions can be drawn from the analyses that were performed, and what next steps should be taken
📢: Visit the codebooks section for a detailed list of database data.
Other userful data sources:
First, log into Code for Philly Slack and join channel #data-hack-chat -> database username and password are a pinned topic in there
Set 2 system variables to allow access to the database; type this in the Console:
Sys.setenv(DATAHACK_DB_USER = "reader")
Sys.setenv(DATAHACK_DB_PASS = "[pwd]") # replace [pwd] with the the password you got from the Slack channel
Run the script /home/connect_to_db_rstudio.R; if you get authentication errors, set the environment variables again via the code above.
docker-compose upHere is a 2 minute screencast of this approach, with unfortunately no sound.
Run:
docker-compose up_env and set your credentials.
Rename it to .env
Run the notebook /home/test_notebook.ipynb
To contribute, you will need to:
Below are a few links to help you better understand some analyses and work that has already been done in this area. These links are for informational purposes only.
The organizing groups are dedicated to creating a hackathon that reflects the diversity of the City of Philadelphia, and to providing a friendly, safe, welcoming, and harrassment-free environment for everyone, regardless of gender, sexual orientation, mental and/or physical ability, ethnicity, socioeconomic status, age, and religion (or lack thereof). This code of conduct outlines our expectations for all those who participate in this hackathon, as well as consequences for unacceptable behavior that contributes to making anyone feel unsafe or unwelcome in our community. Anyone who violates this code of conduct may be sanctioned or expelled from the hackathon at the discretion of the leadership team. Participants are responsible for knowing and abiding by these rules.
We expect all participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all venues–online and in-person–as well as in all one-on-one communications pertaining to community business. This code of conduct and its related procedures also applies to unacceptable behavior occurring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members.
This Code of Conduct was adapted for the hackathon from the Code for Philly Code of Conduct and the R-Ladies Code of Conduct.
The following behaviors are expected and requested of all hackathon participants:
The following behaviors are considered harassment and are unacceptable among participants of this hackathon:
If you are being harassed by another participant, notice that someone else is being harassed, or have any other concerns, please contact the leadership team via safespace@codeforphilly.org.
Leadership team members are available to help participants engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. Organizers will also provide escorts as desired by the person experiencing distress.
We will respect confidentiality requests for the purpose of protecting victims of abuse. At our discretion, we may publicly name a person about whom we’ve received harassment complaints, or privately warn third parties about them, if we believe that doing so will increase the safety of our participants or the general public. We will not name harassment victims without their affirmative consent.
If a participant is found to be in violation of this code of conduct, they will be informed verbally and/or in writing by the leadership team. Participants asked to stop any harassing behavior are expected to comply immediately. If the individual is not an immediate threat to the community, they will be issued a warning. If, after receiving an initial warning, the individual is found to have violated the code of conduct a second time, that individual can be expelled from the hackathon. When expelled, they will not be granted access to in-person events and will be removed from all hackathon-related social media platforms. Consideration will be given at all times to the severity of a given code of conduct violation. If it is in the best interest of the community for an individual to immediately be expelled from the hackathon, it is the discretion of the leadership team to do so.
If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the leadership team with a concise description of your grievance.
Should you need to get in touch with the leadership team, you can reach out to us over Code for Philly Slack:
marieke)karla)machow)joey_logan)beckerfuffle)dwlarson10)