Complete
Every requested task and usable file is present by the deadline.
Six demos + one hackathon
Assignments
Weekly assignments are checked for completion. The final hackathon assesses the quality of the group’s analysis and report.
Assignments begin in Week 2. Nothing assessed is due before Session 1. Demo 1 and the Swirl lessons are due when Session 2 begins on Sep. 25 at 09:15. DataCamp starts after Session 2. Its first block is due Oct. 2 at 09:15.
What you will do
Sessions 1–6 each produce one individual demo. You begin it during class, finish any remaining checklist items afterward, and push the named files to your private GitHub repository by the deadline. The final is a four-hour group hackathon completed and submitted in class.
- Complete the short “Before class” items on the session page.
- Follow the demonstrated Orange workflow or the required R-track equivalent.
- Save the workflow or script under the exact filenames listed. Include the required outputs, settings, and text checks.
- Commit and push the work. Verify every required file on github.com.
R foundations
Everyone completes the six blocks below. Each block is worth one completion mark. DataCamp materials are managed through the online course classroom and are listed here without public course links. The instructor adds everyone after Session 1, once attendance confirms the group. DataCamp will send an email notification when you are added.
These programming exercises are separate from the weekly demos. When both are assigned, they share the same Friday deadline at 09:15.
| Assignment | Due | For lesson | Complete |
|---|---|---|---|
| Swirl · R Programming | Sep. 25 · 09:15 | Session 2 · Text Preprocessing | Lessons 1 Basic Building Blocks, 2 Workspace and Files, 4 Vectors, 6 Subsetting Vectors, 7 Matrices and Data Frames, and 12 Looking at Data |
| DataCamp · Introduction to R · Block 1 | Oct. 2 · 09:15 | Session 3 · Descriptive Patterns | Chapter 1 Intro to basics |
| DataCamp · Introduction to R · Block 2 | Oct. 9 · 09:15 | Session 4 · Clustering and Similarity | Chapters 2 Vectors and 3 Matrices |
| DataCamp · Introduction to R · Block 3 | Oct. 16 · 09:15 | Session 5 · Sentiment Analysis and Clustering | Chapters 4 Factors, 5 Data frames, and 6 Lists |
| DataCamp · Intermediate R · Block 4 | Oct. 30 · 09:15 | Session 6 · Topic Modeling | Chapters 1 Conditionals and Control Flow and 2 Loops |
| DataCamp · Intermediate R · Block 5 | Nov. 6 · 09:15 | Hackathon preparation | Chapters 3 Functions, 4 The apply family, and 5 Utilities |
How completion is recorded
DataCamp: completion is checked through the course classroom dashboard. No screenshots are required.
Swirl: save one completion screenshot per assigned lesson, showing the lesson name and completion message. Name each file by its lesson number: swirl-01.png, swirl-02.png, swirl-04.png, swirl-06.png, swirl-07.png, and swirl-12.png. Commit and push all six to r-learning/ by the deadline.
BA2 review alternatives
Students who completed these activities in BA2 may repeat both complete DataCamp courses as review. With advance approval, the instructor may assign equivalent Swirl or DataCamp work for additional learning. Alternative work follows the same five weekly deadlines and is worth the same six completion marks. The weekly R scripts and R-only hackathon remain required.
Weekly demos
Demos 1–5 are due at 09:15 on the same Friday as the corresponding R foundations work. Demo 6 is due on Friday, Nov. 6, at 09:15.
| Demo and lesson | Due | Repository folder | What must be evident | Details |
|---|---|---|---|---|
| Demo 1 · Session 1 · Introduction to Text as Data | Sep. 25, 09:15 | demos/01-setup/ |
Repository structure, README, provenance record, and two pushed commits | View exact filenames and checklist |
| Demo 2 · Session 2 · Text Preprocessing | Oct. 2, 09:15 | demos/02-preprocessing/ |
Preprocessing workflow, clean word cloud, and a README with the settings | View exact filenames and checklist |
| Demo 3 · Session 3 · Descriptive Patterns | Oct. 9, 09:15 | demos/03-descriptive-patterns/ |
Bag-of-words workflow, count and TF-IDF word clouds and top-ten bar charts, and a README with a reflection | View exact filenames and checklist |
| Demo 4 · Session 4 · Clustering and Similarity | Oct. 16, 09:15 | demos/04-clustering/ |
Clustering workflow, dendrogram of 3 to 5 groups, two further figures or tables, and a README that names the groups | View exact filenames and checklist |
| Demo 5 · Session 5 · Sentiment Analysis and Clustering | Oct. 30, 09:15 | demos/05-sentiment/ |
Sentiment workflow, score chart, manual checks of six sentences, and a paragraph on what the 일본 clusters and their scores show | View exact filenames and checklist |
| Demo 6 · Session 6 · Topic Modeling | Nov. 6, 09:15 | demos/06-topic-modeling/ |
Topic-model workflow, topic and document outputs, three text checks, and shared hackathon scope | Exact checklist opens Oct. 16 |
All deadlines are in Leiden local time. This overview names the lesson, expected output, and deadline from the beginning of the course. Each session page supplies the exact filenames and completion checklist.
BA2 review track
Students on the BA2 review track complete each demo in R, following its assignment sheet.
- Demo 2 · R assignment sheet (PDF)
- Demo 3 · R assignment sheet (PDF)
- Demo 4 · R assignment sheet (PDF)
Submission expectations
Demo 1 follows the repository setup checklist on the Session 1 page. For analysis demos (2–6), include the following items as specified by the session checklist.
- A short
README.mdrecording the corpus, software track, relevant settings, and completed tasks. - A workflow or script that opens from the repository.
- The specifically named figures, tables, screenshots, or text-check files.
- A final commit pushed before the deadline and visible on github.com.
Files saved only on your computer, empty placeholder files, broken workflows/scripts, or links you have not granted the instructor permission to open do not count as submitted. Use the recommended repository structure and never commit restricted corpus files unless the instructions explicitly permit it.
Completion scale
Partial
One or more checklist items are missing or unusable, or the submission arrives within seven days after the deadline.
Missing
No required files are submitted, or the submission arrives more than seven days late.
The weekly demo score records whether you did what was requested. It does not reward originality, sophistication, or the quality of the interpretation. Technical feedback prepares you for the hackathon. Each R foundation block is scored separately. Complete work earns 1 mark, partial work earns 0.5, and missing work earns 0.
Attendance and deliverables (30%)
- Six demos × two points = 12 points.
- Six R foundation blocks × one point = 6 points.
- Six regular-session attendance marks × one point = 6 points.
- Total earned points are scaled from 24 to the 30% course component.
Final hackathon (70%)
The final project is completed in class on Nov. 13 from 09:15 to 13:15 in groups of two or three. Each group uses one prepared course corpus and one main method. The group must also inspect at least three passages. The submission is a private group repository with a reproducible workflow or script, two or three figures or tables, provenance and contribution records, and an 800–1,200-word PDF report. The complete brief and approved corpus menu open Oct. 30.
Submission check
Complete these checks before every deadline.
- Open the repository on github.com.
- Navigate to the correct folder.
- Open the workflow/script and every required output.
- Compare the folder against the published checklist.
- Confirm the latest commit time is before the deadline.