"Millennials are more pessimistic about surviving the pandemic, though they are least at risk" - a pull quote from the following economist article - https://www.economist.com/graphic-detail/2020/07/21/young-people-see-covid-19-as-a-bigger-threat-than-their-elders-do
There are multiple articles about the spread of misinformation as a result of young American's adoption of social media as their source of news and information. This misinformation cuts "both ways" as it were; with some thinking they have the evidence from Facebook rants that Masks do nothing or from blue check twitter "journalists" that everyone is dying in the streets and it's the apocalypse.
The truth, is much more nuanced and boring then either of these sensationalized, click-bate argument generation factories.
- You want your friends and family to find their way back to normal through illuminating data
- You want to build a dashboard where they can see their risk associated with C19 and put it into perspective of other risks they face every day (disease or otherwise)
- You want to build a simple web app in order to illustrate this
- You don't want to track anyone, just provide access so people can form their own knowledge with accurate information
Model these entities, relationships, and any attributes you can think of that are relevant to risk factors (at least 5 per entity, the more robust the better) using Diagrams.net
- Patient (age, etc)
- Geographic Location (Country, etc)
- Occupation (Close contact?, ect)
- Hospitals (ICU max, etc)
- Behavior (partying, etc)
- Risk (level, etc)
- Any additional entities you can think of that would make sense in seeking to model this scenario
If these suggested names don't make sense to you or you wish to modify the model completely then please feel free to do so. The above is merely a suggestion to get you going in the right direction, thinking about what would be involved.
- Create a Conceptual diagram that expresses the model of data above using https://www.diagrams.net/
(save this as a file for later because we'll keep building off of it)
- Create example Tuples for each entity to illustrate how this data might be structured in a database table
- Try to highlight what would be a primary or foreign key relationship
- Also try and guess cardinality where relevant
example: (1) Hospital has (N) patients
- Explain your diagram; entities, relationships, why tuples should be laid out the way you chose and justify why you'd build it the way you've decided
- Write this trying to explain the problem space to a less technical friend or how you'd explain it to a non-technical manager
- Don't worry about word count, focus on accuracy of your diagram and its robustness
- The write up is intended to help you find your words more readily in the video.
- Make a video explaining your diagram
- Explain why you think data should be structured the way you have proposed
- Why do you think these entities make sense?
- What relationships exist?
- What attributes are required to ensure the relationships exist?
- Describe at least one of the tuples and show it in a spreadsheet
- What fields help form primary / foreign key relationships
- Embed your screen cast in the bottom of your blog post
- Submit a link to your article in #lab2-er-diagram
channel on Slack
- This is due by Sunday at 11:59pm
