Data Visualization & Graphics

Semester: Fall-2026

Course number: Math-1505

Course description

Effective graphical displays of data allow the viewer to understand the structure of a complex dataset at a glance. Graphical displays have many purposes from an initial exploration of a dataset to presentation of final results. This course provides an introduction to using the statistical software package R, and python, to create appropriate and illuminating visual displays of data. We will discuss the properties that make a visual display of data clear, accurate, and powerful and learn the tools to create effective visualizations. In addition, students will learn some of the most common abuses of data visualization and how to recognize (and correct) misleading displays of data. Classroom material will be accompanied by hands-on experience using statistical software with an emphasis on creating transparent, reproducible statistical analyses and visualizations.

Course details

The following are the email addresses for the instructional team.

Professors

• Professor James Hickman
 • Email: jh2343@georgetown.edu
 • Office: Car Barn 207
 • Office hours scheduling link: click here

Teaching assistants

The following are the email addresses for the teaching assistants.

• Matthew Long: mtl75@georgetown.edu

Office hours

Office hours with TAs and Professors are available at various times.

  • Unless otherwise requested, office hours will be virtual using video conferencing.
  • If the available times in the scheduling links do not work for you, please email a member of the instructional team to arrange an alternative time slot.

All TAs offer one-on-one office hours, depending on their schedules and availability.

Office hours with TAs can be arranged via the email addresses listed above.

Important: If you would like to discuss code during office hours, please email a copy of your code to the TA or Professor at least 8 hours before your meeting.

Textbooks

• This course has no official textbook. Notes will be provided online throughout the semester.

Meeting details

Unless otherwise stated, meetings are in person with the following details:

• Math-1505: Tuesday and Thursday from 11AM - 12:15 PM (EST) at Walsh: 497

Note: See the calendar page fore more details on specific meeting dates.

Topic Summary

Note: See course calendar Page for tentative plan of topics.

Course structure

  • The course consists of 14 weeks, with two meetings per week.

Lectures (1.25 hr)

  • Each week will contain a 1.25-hour lecture
  • Demos: some weeks there will be at-home recordings of technical coding demonstrations.
  • The lecture covers a large amount of information with Q&A at the end.

Outside of class

  • You should expect to spend around 6 to 10 hours on it per week outside of class.

Google-Spaces

Google-Spaces is the main way the instructional team will answer questions. All students MUST join the Google-Spaces workspace using the invitation link:

You may use Google-Spaces to:

  • Discuss ideas and approaches to problems
  • Resolve technical/code issues
  • Post small, specific code snippets (just a few lines)

Access Google-Spaces via your browser or mobile device.

  • WARNING: Google-Spaces is public—keep all communication professional, respectful, and relevant. Inappropriate or unprofessional content will result in disciplinary action. If unsure, consult the professor before posting.

Note: Google-Spaces is not an instant-response service. Expected reply times:

  • M-F, 9AM-5PM (EST): responses in 2-6 hours
  • M-F after 5PM: responses by the next day
  • Weekend: responses on Monday

We do not answer questions on Google-Spaces in the eight hours before an assignment deadline. Start assignments early and ask questions ahead of time.

Laptops

To take this class, you must have a laptop (Windows, Linux, or Mac), reliable internet (with backup), microphone, speakers, and camera.

Grading

Point system

Your grade will be determined using a simple points system. Points will be allocated based on performance and/or completion of course deliverables. Each deliverable will earn you a specified number of points. At the end of the semester, there will be some final number of total possible points, typically around 1000 total points. Your final grade will be computed using the following formula.

GRADE PERCENTAGE = 100*POINTS_EARNED/TOTAL_POINTS_POSSIBLE

Where the letter grade is computed using the following rules:

  • 95% or more points: A
  • 90% to 94% points: A-
  • 87% to 89% points: B+
  • 84% to 86% points: B
  • 80% to 83% points: B-
  • 77% to 79% points: C+
  • 74% to 76% points: C
  • 70% to 73% points: C-
  • 67% to 69% points: D+
  • 60% to 66% points: D
  • 59% of fewer points: F

NOTE: Unless otherwise stated, for group deliverables, all students will receive the SAME grade (except for points associated with peer-evaluations)

General Expectations

Many assignments in this course are open-ended, meaning there are numerous valid paths to success, and simply submitting a deliverable does not guarantee an “A.” We use a holistic grading approach, evaluating your submission as a complete package and comparing it against peer work rather than assigning specific point values to individual elements. Therefore, if your work is merely “good” but leaves obvious room for improvement, your grade will reflect that. To earn a high score, your deliverable must reflect professional expectations by not only meeting but exceeding core requirements. Top grades are awarded to submissions that demonstrate deep critical thinking, significant effort, and creativity, while featuring precise grammar, an organized layout that is easy to review, and publication-quality visualizations.

Grade bracket interpretation

Typically, we will compute grades based on the extent to which the quality of your work falls into the following brackets.

  • Excellent: A (100%) The deliverable component was taken very seriously, correctly completed, done professionally, and appears to exceed all expectations.
  • Good: A- (90%) The deliverable component was seriously attempted, meets expectations, and does not have any missing components. However, there are a few issues that need minor improvement.
  • Acceptable: B (80%) The deliverable component was attempted and mostly meets expectations. However, there are some minor missing requirements, or parts that are incorrect and require moderate improvement.
  • Needs improvement: C (70%) The deliverable component was attempted but is below expectations. Several parts are incorrect and need significant improvements, or show some lack of effort.
  • Needs serious improvement: D (60%) The deliverable component was attempted but is significantly below expectations. It has many serious issues, several missing components, or obvious lack of effort.
  • Unacceptable: (0%) The deliverable component was not attempted, or is largely blank, or is otherwise somehow unacceptable.

Deliverables

Definition: A deliverable is anything that you turn in for a grade.

Due dates

  • Due dates in this class will typically be at 11:59PM (EST) on Wednesday or Thursday.
    • However, this may occasionally vary due to holidays and when the assignment was made available.
  • Due dates will never fall on weekends or holidays.
  • Deliverables will be made available to all sections at the same time, and will be the same for all sections.
  • This is done so that all sections have the same amount of time to work on the assignment.
  • The official due dates for this class will be available in two locations.
    • On each assignment’s associated Canvas page
    • On the following Canvas page (click here).

Shared folder

All deliverables will be distributed through a shared cloud-based folder, organized into subfolders such as “homeworks”, “labs”, “codes”, “projects”, and more.

The link below provides access to these IMPORTANT course resources. New materials will be added throughout the semester.

If you notice that any files are missing, please contact your professor immediately.

We recommend bookmarking the shared folder link for easy access.

https://drive.google.com/drive/folders/1Ic_QdpLcWe_WgUUZVfHiH5jSLY5OHVCK?usp=sharing

Rendering assignments

For .ipynb, .qmd, and .rmd assignments, you will need to render the assignment to a .html or .pdf file.

When doing so, make sure to embed resources, such as images, so that the assignment can be viewed by the graders without issues, failure to do so will result in a deduction.

In the YAML header of your .qmd or .rmd file, add the following before rendering, e.g. quarto render filename.qmd:

---
format:
  html:
    embed-resources: true
--- 

Summary of deliverables

Project

Early in the semester, the project description will be added in the shared folder’s Project sub-folder. The project expectations will also be introduced in class.

Homeworks

  • DESCRIPTION: Every week there will be a technical homework (HW) which you will have around one week to complete. This will include coding exercise and may also include pen and paperwork.
  • SUBMISSION AND GRADING: More details will be included on each HW assignment with submission and grading details.
  • GRADING: Homeworks will be graded using assignment specific rubrics provided on the assignment’s Canvas page.

Quizzes

There will be weekly in-class, closed-book, pen-and-paper quizzes, usually held during the second class meeting each week. These are short, one-page quizzes designed to check your understanding of the week’s material. If you pay attention and participate in class, you should have no problem succeeding on these quizzes.

  • Submission: Quizzes will be completed by hand and turned in during class.
  • Closed-book: No external resources (internet, phone, textbooks, etc.) are allowed. You may use a basic calculator (not your phone; e.g., TI-84). If you are seen with your phone out during a quiz, you will automatically receive a zero.

Point breakdown

Important: The following is subject to minor changes throughout the semester. If deliverables are cancelled during the semester, or converted to extra credit, then the total points possible will be reduced from 1000, in accordance with the cancelled deliverable’s available points. This will have a slight impact on the relative fraction of points associated with each deliverable type, e.g. quizzes vs homeworks.

The following is the approximate point breakdown based on deliverable type.

Note: There will be no final exam in this class, instead we will have a final project.

  • Final Project → 22% (220 points)
    • The project will have multiple components, including a code repository, a narrative website, and a presentation.
    • The project itself will be due during finals week. However, we will hold a “project presentation” during the last weeks of class. This presentation is an opportunity to showcase the current state of your project; it does not need to be completely finished—something in the 75–90% complete range is totally fine. The main purpose is to share your progress with the class and receive feedback from your peers.
  • Quizzes → 36% (12 quizzes, 30 points per quiz = 360 points)
  • Homeworks → 42% (12 homeworks, 35 points per homework = 420 points)
  • Total → 100% (1000=220+360+420 points)

Late penalties

All due dates will be specified in Canvas at the following link click here

General Recommendation

Due dates are when the deliverable MUST be completed by, NOT when they SHOULD be completed by. You should get things done well before the due date. DO NOT WAIT UNTIL THE LAST MINUTE TO COMPLETE DELIVERABLES. Proper time management will be extremely important in your future careers, the same is true in this class!

Also, do not expect urgent help on something at the last minute. For example, do not expect prompt responses from TAs or Instructors at 7PM for an assignment that is due at 11:59PM.

Quizzes

Quizzes are in person and must be done during the class period in which they are given.

  • Quiz make-up: With the exception of the first two weeks of class, quizzes will not be available outside of class. There are no rescheduling or make-up quizzes. If you miss class for any reason, you will not be able to take the quiz, period. You will only have one attempt; retakes are not allowed.

  • Accommodating class absences:

    • The THREE lowest quiz scores will be dropped for all students. This means you can miss up to 3 quizzes without it affecting your grade. These lowest three scores will be marked as excused in Canvas, making them effectively invisible to the grade calculation (see below for more details).
    • If you are absent, the first 3 missed quizzes will be marked as excused in Canvas, after that additional missed quizzes will be entered as 0.
    • If you attend all classes then the lowest 3 quiz grades will be excused at the end of the semester.
  • Students with ARC accommodations should reach out to their instructor to coordinate arrangements (e.g. arriving early or staying after class to allow extra time).

Note on excused grades in Canvas

In Canvas, an “excused” grade removes the assignment from a student’s total grade calculation.

  • The student doesn’t need to submit it.
  • The assignment is excluded from their overall percentage.

Example

Consider a course which has 2 assignments, each worth 10 points:

Case 1: Left as zero

  • Assignment 1: 8/10
  • Assignment 2: 0/10
  • Final grade = (8 + 0) ÷ 20 = 40%

Case 2: Excused

  • Assignment 1: 8/10
  • Assignment 2: 0/10 but Excused
  • Final grade = 8 ÷ 10 = 80%

So changing a 0 to Excused removes the penalty, and the grade calculation ignores that assignment.

Everything other than quizzes

For all other deliverables, late penalties for submissions past the Canvas deadline obey the following rules;

  • 0 to 24 hours late: 0% deduction (grace period)
    • We understand that the grace period essentially only delays the deadline by a day. However, students in the past have generally found it beneficial as a buffer to provide a bit more time for last minute issues.
  • 24 to 48 hours late: 5% deduction
  • 48 to 96 hours late: 10% deduction
  • 96 to 120 hours late: 20% deduction
  • 120 or more hours late: 30% deduction

Important: Beyond this, you can submit late deliverables any time during the semester. However, you will receive a maximum of 70% for the submission. The deliverable will be graded as usual on top of the 30% deduction.

Extensions

Giving one student an extension means that we need to give the option for extensions to all students, which is logistically infeasible. Therefore we are not granting extensions for assignments.

DO NOT EMAIL US TO ASK FOR EXTENSIONS, THERE ARE NO EXTENSIONS FOR THIS CLASS

We’ve allowed extensions in the past and they were problematic, causing students to fall behind.

We know that “life happens”, to accommodate this we are instead using very lenient submission policies, including:

    1. Long submission windows to complete the assignments (e.g. a week for a HW assignment)
    1. Provided a generous grace period after the due date.
    1. Long late windows with lax late penalties
    1. Ability to submit anything, anytime in the semester, for up to 70% credit.

Obviously there are highly rare and extreme life events, such as breaking a bone, giving birth, losing one or more toes, serious car-accidents, and deaths in the family, in such cases, reach out to the professor and explain the situation. Colds, Flu, and other common illness do not meet the criteria for “extreme life events”. If you are worried about getting sick, start the assignment early before you get ill. 

AI Usage Guidelines

The integration of Artificial Intelligence (AI) and Large Language Models (LLMs) into academic and professional workflows is a powerful, and increasingly unavoidable reality. These tools are double-edged swords, they can be incredible productivity accelerators or detrimental shortcuts that bypass essential learning. The following guidelines establish how to use AI ethically, responsibly, and effectively.

1. Core Principles for AI Usage

  • Use Common Sense: If you feel like you might be crossing a line, you probably are. If you are doing something you would not openly discuss with your professor, then it is likely a form of academic dishonesty. When in doubt, ask for clarification.
  • Prioritize Growth: A good sanity check for ethical AI use is asking yourself: Is this genuinely helping me grow into a better, more well-rounded professional? Excessive reliance on AI as a shortcut will eventually catch up to you, especially in technical job interviews where fundamental knowledge is tested. Your brain is a muscle; excessive shortcuts weaken it.
  • Be Honest and Transparent: If you use AI for a deliverable, you are required to include a disclosure section concisely documenting how you utilized the tools.

2. Different Ai Usage Regimes

When integrating Artificial Intelligence (AI) into your workflow, it is crucial to recognize that there are at least two distinct regimes of AI usage. And you should always know where you stand and try to tailor your usage of AI to align with your current skill level. How you interact with AI in these two regimes varies dramatically.

  1. The Educational Context: You are a student actively learning and developing a new skill set. In this case you need to force yourself to learn the fundamentals before going “full steam ahead” with Ai, this is hard to force yourself to do, but essential.
  2. The Production Context: You are a seasoned professional who has already mastered a skill set and is using AI to scale your output. In this regime it is reasonable to leverage Ai to it’s full capacity.

Calculator Analogy: Imagine if, when learning basic addition, subtraction, and multiplication, you completely ignored the endeavor because calculators existed. It would have been easy in the moment, but highly detrimental to your education. You would be completely unable to do quick mental math, estimate percentages, or intuitively understand numbers.

The situation with AI is analogous. If you rely on AI to do the thinking for you now, you will lose the ability to think critically, verify logic, and understand the limits of what you produce. We highly recommend stepping back and fully embracing an educational mindset until you are completely competent in the skills you are learning.

Generally, Only use AI for tasks you already know how to do easily without it.

  • Learn the basics first: You must learn to “ride a bicycle” (understand the fundamentals) before you get on a “motorcycle” (use AI to speed up the process).
  • Accelerate known skills: Once you have mastered a topic, you can use AI to do it faster. This frees up your mental bandwidth for more intellectually demanding tasks.

3. Acceptable vs. Unacceptable Use Cases

Caution: LLMs frequently “hallucinate” or generate inaccurate information. You are solely responsible for verifying the accuracy of any AI-assisted output.

Acceptable Use Cases (Refinement & Assistance)

AI should be used as an assistant to refine your original thoughts and work, or to help you understand complex topics.

  • Supplemental Learning: Asking for basic explanations of concepts, assignments, or instructions.
  • Research & Brainstorming: Generating ideas for projects or clarifying complex topics.
  • Programming Assistance: Asking the AI to explain what a specific block of code does or to automate formatting for code comments.
  • Writing Improvement: Proofreading, summarizing documents, or making your original text more concise.
  • Career Preparation & Accessibility: Simulating mock interviews, practicing communication, or using AI as an assistive technology for learning disabilities.

Unacceptable Use Cases (Cheating & Plagiarism)

Do not use AI to bypass the learning process. The following will be treated as academic dishonesty:

  • Full Content Generation: Generating entire essays, codebases, or assignments from scratch without significant original contribution.
  • Exams & Homework: Using AI during exams or to automatically generate homework solutions.
  • Ghostwriting & Impersonation: Having AI write personal statements or substituting AI-generated responses as your own authentic voice.
  • False Justifications: Using AI to generate false explanations for incorrect answers to feign understanding.
  • Unauthorized Collaboration: Using AI when explicitly prohibited by assignment instructions.

4. AI and Coding: Striving for Symbiosis

If you rely entirely on AI to code, your skills are limited to the capabilities of the AI, which is not a very valuable position. You should aim to become a professional who is force-multiplied by AI. Together, you and the AI should be significantly more valuable than either alone. Working symbiotically with these tools is what will make you a highly effective problem solver and coder.

  • Small Snippets are Okay: When getting started, using AI to generate small, isolated snippets or explain syntax is acceptable (similar to using StackOverflow in the past).
  • No Full Generation Until Mastery: It is prohibited to use AI for full code generation until you are a master-level coder capable of debugging virtually anything in your chosen programming language.
  • Avoid Agentic Workflows for Now: If you cannot effectively debug a program from scratch, do not use fully agentic tools (like Claude Code). If you don’t know what the AI is doing under the hood, you won’t know how to fix it when it breaks.

6. Documentation and Disclosure of AI Tool Use

  • Always cite any content, ideas, or code taken from external sources (including websites, LLM tools, papers, etc.).
  • Always be transparent about your use of AI tools.

Guidelines for disclosing LLM (AI) tool usage:

  • Routine Use: Keep an updated LLM Transparency section (e.g., in your project or homework documentation) summarizing how you use LLM tools for non-content-generating tasks (e.g., reformatting your own work, adding comments to your handwritten code, proofreading, or document summarization).

  • Example Disclosure Statement:

This statement can be included in a project report or as a comment block at the beginning of your coding assignment.

## LLM (AI Tools) Transparency Statement

For this assignment, I used Large Language Model (LLM) AI tools in line with course guidelines. 

Usage included the following:

**1. Idea Generation:**  
- Used ChatGPT for brainstorming topics and clarifying assignment requirements. 
- All suggestions were critically evaluated and adapted as needed.

**2. Writing and Editing:**  
- Used AI to proofread, reformat, and improve clarity of my own draft content. 
Summaries or suggestions from AI were always rewritten in my own words.

**3. Coding Support:**  
- Asked AI for explanations of code, debugging tips, and to generate comments on code I wrote. 
Used AI-generated code snippets only for reference or learning, not as direct submissions.

**4. Formatting Help:**  
- Used AI for citation formatting and LaTeX/Markdown syntax questions but personally wrote all citations.

**Limitations:**  
- AI served only as an aid for explanation, editing, and brainstorming.
- It was not used for producing large sections of original content or entire solutions.

*All AI-assisted work was manually reviewed and revised to ensure authenticity and meet course standards.*

Failure to cite or disclose use of AI or external sources may be considered a violation of academic integrity. When in doubt, err on the side of transparency.

7. Displinary actions & Academic Integrity

Verification of Understanding and Displinary actions

The instructional team reserves the right to assess you on any submitted content to verify your comprehension. For a coding project, we may randomly select sections and require you to:

  • Explain the code line-by-line and identify data types.
  • Discuss potential edge cases.
  • Trace the logic of loops and computational workflows manually on paper.

If you cannot explain your submitted work satisfactorily, penalties will range from a grade deduction to a full Georgetown Honor Council review for plagiarism.

Georgetown University Honor Code

Academic integrity is central to the learning process. Georgetown University enforces a strict zero-tolerance Plagiarism Policy. Plagiarism, intentional or unintentional, includes presenting AI-generated text, code, mathematical solutions, or ideas as your own without proper citation.

All violations will be reported to the Georgetown Honor Council. Penalties include, but are not limited to:

  • A zero/failing grade for the assignment or course.
  • A permanent mark on your official transcript.
  • Termination from the program or revocation of degrees.

As members of the Georgetown academic community, you are expected to strive for excellence in both scholarship and character.

Getting help

The instructional team wants everyone to succeed!

If you are struggling in this class, do not try to “go it alone”, reach out for help ASAP!

The following are recommendations for students struggling in the class.

Recommendations

Join the Google-Spaces using the following invitation link

https://chat.google.com/room/AAQAsMnOG0Q?cls=7

  1. Form study groups: Start reaching out to classmates in the class to form study groups.
  2. Attend office hours: Start attending office hours with TAs and professors for extra help
  3. Stay active on Google-Spaces:
    1. Google-Spaces is a place meant for you to reach out quickly and ask questions, please make sure you are using this resource.
    2. Also, there are various clarifications about the deliverables.
    3. If you have a question, you are probably not the only one who does.
    4. Make sure you are keeping up to date on the Google-Spaces conversations
  4. Use the code we provide: Make sure you are familiarizing yourself with the codes and other content provided by the instructional team
  5. Review bootcamp material: If you need extra help with R or python fundamentals then please review the bootcamp materials (see below for link).
  6. Reach out to the ARC program: The Academic Resource Center (ARC) is the campus office responsible for reviewing medical documentation and determining reasonable accommodations to students with disabilities.

Asking questions

RECOMMENDED COMMUNICATION ORDER: Please follow the following communication hierarchy

  1. Ask a friend: If you question can be answered by a class-mate, in a manner that does not constitute cheating, then that is typically the best place to start.
  2. Public channel: If your question can be addressed in a relevant public Google-Spaces channel, then do so. Also, remember Google-Spaces IS SEARCHABLE!
  3. Email TAs: Some questions about code or the course are not suitable for a public channels. In this case email one of the TAs. TAs reserve the right to tell you to post the question on Google-Spaces if they feel it belongs on the public channel (or forward it to the professors)
  4. Office hours: If there is a persistent bug that you can’t figure out, then please attend office hours with a TA or instructor.
  5. Email one or more professor(s): If you feel your question can ONLY be addressed by your professor, then don’t hesitate to email them, also feel free to CC the other professors on such emails.

Academic Integrity & Plagiarism Policy

Plagiarism is the presentation of another person’s ideas, text, code, or data as your own, whether intentional or not. All students are expected to maintain the highest standards of academic integrity and adhere strictly to the Georgetown University Honor Code.

Individual Work vs. Collaboration

Unless explicitly stated as a group project, all assignments are strictly individual work.

  • Allowed Collaboration: We encourage discussing high-level ideas, problem-solving strategies, and general technical issues in labs, office hours, and on public channels (e.g., Google-Spaces).
  • Prohibited Behavior: You may not share your actual work or code with others, even “just to help out.” If you share your work, both the sharer and the receiver are guilty of cheating.

Using External Sources

You are welcome to use online resources to learn, but you must properly attribute anything you use.

  • Code Citation: You may use snippets from sites like StackOverflow unless instructed otherwise, but you must provide the source URL as a comment in your code (e.g., # Source: modified from [URL]). Do not copy entire assignment solutions from platforms like GitHub. Note: Trivial syntax queries (e.g., “how to write a for loop in Python”) do not require citation.
  • Text Citation: Never copy text verbatim from external sources without quotation marks and an in-line academic citation. Whenever possible, synthesize the information and express it in your own words rather than relying on direct quotes.
  • When in doubt, ask! If you are unsure if your use of a resource constitutes plagiarism, ask the instructional team before submitting.

Enforcement and Penalties

We employ a Zero Tolerance Policy for cheating. All deliverables—including code—are checked against web resources and every other student’s submission. High levels of similarity will be investigated.

If you are found in violation of the Honor Code, the following will occur:

  1. Automatic Zero: You will receive a zero for the relevant assignment.
  2. Department Report: The incident will be reported to the Department.
  3. Honor Council Report: You will be reported to the Georgetown Honor Council. This typically results in a permanent mark on your official transcript, and repeated or severe offenses can lead to course failure, expulsion, or revocation of degrees.

Communication Guidelines

To manage our large class effectively, please follow these communication standards for all interactions.

General Questions vs. Private Inquiries

  • Public Questions (Coursework, bugs, software): Post these to the relevant public channel on Google-Spaces so everyone benefits from the answer. Do not share large chunks of code or homework solutions.
  • Personal Questions (Grades, private matters): Email your professor directly. Do not Direct Message (DM) professors on Google-Spaces unless they contact you first, as DMs are easily lost.

Code of Conduct

These rules apply to all forms of class communication, both in-person and digital (e.g., Google-Spaces, Canvas, GitHub).

Pledge & Standards

We are committed to providing a welcoming, harassment-free, and inclusive environment for everyone, regardless of background, identity, or ability.

  • Expected Behavior: Demonstrate empathy, respect differing viewpoints, accept constructive feedback gracefully, and prioritize the community’s well-being.
  • Unacceptable Behavior: Harassment, sexualized language/imagery, trolling, personal/political attacks, or using offensive usernames/profile pictures on any class platform.

Course Expectations

Student Responsibilities:

  • Read first: Consult all relevant class materials, syllabi, and announcements before asking a question.
  • Provide context: When asking about class materials, include quotes or links.
  • Justify grade disputes: Include a clear explanation of why an alternative grade is warranted.
  • Be respectful: Submit queries and feedback politely; do not pressure or badger the instructional team.

Instructional Team Responsibilities:

  • Respond respectfully: Handle all student queries with collegiality and professionalism.
  • Provide resources: Direct students to existing class materials when appropriate.
  • Offer constructive feedback: Ensure all criticism is professional and helps the student improve.

Scope and Enforcement

This Code of Conduct applies to all class spaces and anywhere an individual officially represents this community.

The instructional team will enforce these standards fairly. Unacceptable behavior may result in removed comments/contributions and will be addressed collaboratively. Severe or repeated violations may be escalated to University staff per Georgetown University’s Code of Student Conduct. All reports are investigated promptly, and reporter privacy is strictly respected.

Additional Resources

Canvas navigation

Canvas can be organized in a number of different ways. Watch the 5-minute Canvas video tutorial to learn more about how Canvas navigation works. We hope this gives you a sense of what Canvas offers and how you can navigate it.

Academic Resource Center

The Academic Resource Center(ARC) is the campus office responsible for reviewing medical documentation and determining reasonable accommodations to students with disabilities.

Counseling and Psychiatric Services (CAPS)

As Georgetown faculty, you are among the most important individuals in some of the students’ lives. They may turn to you when they are struggling and in times of need, or you may be one of the first to notice when they are distressed. The CAPS has tips for faculty on how to deal with struggling or distressed students.

Emergency Preparedness and HOYAlert

We encourage all faculty to become familiar with Georgetown’s Office of Emergency Managementand sign up for HOYAlert in order to receive important safety and University operating status updates. Faculty teaching at the Georgetown Downtown campus might also want to sign up for AlertDC to receive safety and traffic updates.

Office of Institutional Compliance and Ethics

The Office of Institutional Compliance and Ethics supports and coordinates many compliance-related activities the University undertakes. This Office, with the endorsement and assistance of the University’s senior leadership, is responsible for leading the development, implementation and operation of the Georgetown Institutional Compliance and Ethics Program.

Office of Institutional Diversity, Equity, and Affirmative Action (IDEAA)

The mission of IDEAA is to promote a deep understanding and appreciation among the diverse members of the University community to result in justice and equality in educational, employment and contracting opportunities, as well as to lead efforts to create an inclusive academic and work environment.

Threat Assessment

Georgetown University established its Threat Assessment program as part of an extensive emergency planning initiative. The program at Georgetown has been developed and implemented to meet current best practices and in accordance with national standards for hazard planning in institutions of higher education and for workplace violence prevention.

Title IX/Sexual Misconduct

Georgetown University and its faculty are committed to supporting survivors and those impacted by sexual misconduct, which includes sexual assault, sexual harassment, relationship violence, and stalking. Georgetown requires faculty members, unless otherwise designated as confidential, to report all disclosures of sexual misconduct to the University Title IX Coordinator or a Deputy Title IX Coordinator. If you disclose an incident of sexual misconduct to a professor in or outside of the classroom (with the exception of disclosures in papers), that faculty member must report the incident to the Title IX Coordinator, or Deputy Title IX Coordinator. The coordinator will, in turn, reach out to the student to provide support, resources, and the option to meet. [Please note that the student is not required to meet with the Title IX coordinator.]. More information about reporting options and resources can be found on the Sexual Misconduct Website

If you would prefer to speak to someone confidentially, Georgetown has a number of fully confidential professional resources that can provide support and assistance. These resources include:

Health Education Services for Sexual Assault Response and Prevention: confidential email sarp@georgetown.edu

Counseling and Psychiatric Services (CAPS): 202.687.6985 or after hours, call (833) 960-3006 to reach Fonemed, a telehealth service; individuals may ask for the on-call CAPS clinician

More information about reporting options and resources can be found on the Sexual Misconduct Website.

https://sexualassault.georgetown.edu/get-help/#Links to an external site.

Jen Schweer, MA, LPC Associate Director of Health Education Services for Sexual Assault Response and Prevention (202) 687-0323 jls242@georgetown.edu (mailto:jls242@georgetown.edu)

Erica Shirley, Trauma Specialist Counseling and Psychiatric Services (CAPS) (202) 687-6985 els54@georgetown.edu (mailto:els54@georgetown.edu)

More information about campus resources and reporting sexual misconduct can be found at http://sexualassault.georgetown.eduLinks to an external site.

Please know that as a faculty member I am committed to supporting survivors of sexual misconduct, including relationship violence and sexual assault. However, university policy also requires me to report any disclosures about sexual misconduct to the Title IX Coordinator, whose role is to coordinate the University’s response to sexual misconduct.

Georgetown has a number of fully confidential professional resources who can provide support and assistance to survivors of sexual assault and other forms of sexual misconduct. These resources include: Getting Help

Special Accommodations

If you believe that you have a disability that will affect your performance in this class, please contact the Academic Resource Center (arc@georgetown.edu) for further information. The center is located in the Leavey Center, Suite 335. The Academic Resource Center is the campus office responsible for reviewing documentation provided by students with disabilities and for determining reasonable accommodations in accordance with the Americans with Disabilities Act (ADA) and University policies.