2 M1U: Course Syllabus
The syllabus for this course is available as a PDF through Canvas. However, it is also reproduced here for the purposes of annotation.
2.1 Overview
2.1.3 Contact Information
- Office—341 Lucille Little Library Bldg.
- Phone—859.218.2294
- Email—spencer.greenhalgh@uky.edu
- Zoom—https://uky.zoom.us/my/greenhalgh
2.1.4 Response Time
During the work week (but not the weekend!), I commit to respond to all emails within 24 hours. I expect you to regularly check Canvas and email for messages from me and to respond quickly.
2.2 Required Materials
This course uses a free custom online textbook based on Creative Commons-licensed works such as Data Feminism, OpenStax’s *Introductory Statistics(), and the “ModernDive” Statistical Inference Via Data Science textbook.
2.3 “Life is Difficult” Statement [inspired by [Dr. Andrew Heiss]
Recent years have been characterized by a global pandemic, increased (and overdue) attention to inequalities and injustices, and stressful political tensions; we might hope that the worst of all of these has passed, but the truth is that none of them have disappeared. This can be a difficult time to be in grad school.
Despite these difficulties, I am fully committed to making sure that you learn everything you were hoping to learn from this class! My late policy and willingness to make accommodations are generous even during normal times, and if your life is being turned upside down, I’m willing to be as flexible as you need me to be—so long as you are active in communicating with me.
If you feel like you’re behind, not understanding everything, or just plain stressed, do not suffer in silence! I’m usually quick to respond to email and more than happy to meet with you.
2.4 Basic Needs Statement [inspired by Dr. Sara Goldrick-Rab]
Any student who has difficulty affording or accessing food to eat every day or who lacks a safe and stable place to live and believes this may affect their performance in the course is urged to contact the Dean of Students and to explore the resources listed at the bottom of this page. Furthermore, please notify me if you are comfortable in doing so.
2.5 Course Information
2.5.1 Course Description
This course will provide a foundation in the area of data science based on data curation and statistical analysis. The primary goal of this course is for students to learn data analysis concepts and techniques that facilitate making decisions from a rich data set. Students will investigate data concepts, metadata creation and interpretation, the general linear model, cluster analysis, and basics of information visualization. At the beginning, this course will introduce fundamentals about data and data standards and methods for organizing, curating, and preserving data for reuse. Then, we will focus on the inferential statistics: drawing conclusions and making decisions from data. This course will help students understand how to use data analysis tools, and especially, provide an opportunity to utilize an open source data analysis tool, R, for data manipulation, analysis, and visualization. Finally, in this course we will discuss diverse issues around data including technologies, behaviors, organizations, policies, and society.
2.5.2 Course Objectives—“I Can Statements”
The following “I can” statements will guide all of the learning and assessment activities throughout this course. Although these objectives have some overlap, activities within each module will clearly and specifically relate to a single objective, and larger assessments will implicitly ask you to demonstrate all of them. As we proceed throughout the semester, you should feel increasingly comfortable making these statements about yourself:
- I can express my understanding of philosophical, ethical, statistical, research, and other concepts underpinning data science.
- I can apply that understanding—in conjunction with R programming—to completing practical projects.
- I can connect conceptual and practical elements of data science to disciplinary and contextual knowledge.
2.5.3 Course Assessment
Your grade for this course will be based on 100 points:
- 90 points – 100.0 points = A
- 80 points – 89.9 points = B
- 70 points – 79.9 points = C
- 0 points – 69.9 points = E
These 100 points come from the following assessment activities, which should all be completed honestly and individually on Canvas:
2.5.3.1 Projects
Throughout the semester, you will complete four projects worth a total of 55 points:
- Project #1: Finding and Evaluating Data (10 points)
- Project #2: Exploring and Describing Data (10 points)
- Project #3: Building and Evaluating Models (10 points)
- Final Project: Reporting Data Analysis (25 points)
Detailed instructions for these projects can be found on Canvas.
2.5.3.2 Participation
Throughout the semester, you will earn 45 points from a series of participation activities. During each of the fifteen modules of the semester, you will complete three reading or participation activities (each worth one point) that will help you extend or apply your understanding of course content; while these activities vary from module to module, a plurality of modules involve annotating a reading from the textbook, completing a programming walkthrough with provided data, and then adapting (some of) the code from the walkthrough to work with your own data.
2.5.4 Late Work Policy
Officially, each assignment is due at 11:59pm on the Sunday night indicated in Canvas. Practically speaking, however, I will grade without penalty (for graded assessments) and provide feedback on (for all assessments) anything that is turned in by the time I begin reviewing that assessment. However, I will not grade or provide feedback on any work that is completed after this time unless you have made other arrangements with me. Naturally, because my schedule varies from week to week and because I try to provide feedback as quickly as possible, your best bet is to turn in your work by the official deadline or—if life has thrown you a curveball—to get in touch with me ahead of time to make other arrangements.
2.5.5 Prep Week
UK policies limit what I can assign during Week 16 of the course. However, I am “permitted to grade student participation,” “collect regularly assigned homework,” and “collect projects” so long as those assignments are scheduled ahead of time and, in the case of projects, there is nothing due during Finals Week. Please note that your final project meets these requirements and is due during Week 16.
2.6 Course Policies
All of the policies listed on this page are in effect for this course.
2.7 Code, Plagiarism, and Generative AI
It is common practice in data science and programming communities to borrow code from other, more knowledgeable programmers. Indeed, many of the weekly activities in this class will explicitly involve copying or adapting code from our textbook, and you might find online or other sources helpful for figuring out how to complete a specific task for your class projects. When done properly, this is not plagiarism—in fact, it is good practice in data science.
Nonetheless, you are ultimately responsible for completing assessments, and plagiarism remains a serious concern for this course. Thus, these rules related to academic offenses are also in effect for this course, and I will not tolerate their violation. If you consult other sources, please ensure that they support (rather than replace) your personal work, effort, initiative, and understanding. It is your responsibility to ensure that you understand what plagiarism is and how to avoid it; when in doubt, reach out to me with your questions.
Along these lines, I strongly discourage you from using any generative AI tool to write code or text for you. AI-generated output can include errors, and as a general rule, if you know enough to catch those errors, you know enough to generate that output yourself; conversely, generating that output yourself will help you further develop your knowledge more than relying on a tool. If you do use any generative AI in completing your work, you must explicitly acknowledge it in your submission—and you will assume responsibility for any errors the tool makes.