HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
BobAdamsEE
SouthParkData
Data & Databases2016–2016
BobAdamsEE / SouthParkData

SouthParkData

.csv files containing script information including: season, episode, character, & line.

2Distinct people
2Mentions
0Explicit recommenders
167GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

.csv files containing script information including: season, episode, character, & line.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval2 dated mentions

Observed mentions: 2016-02-10 15:15:50 UTC to 2016-02-15 12:36:25 UTC.

012016-02-10 12:00:00 UTC to 2016-02-10 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 10, 12:002016-02-10 18:00:00 UTC to 2016-02-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-11 00:00:00 UTC to 2016-02-11 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-11 06:00:00 UTC to 2016-02-11 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-11 12:00:00 UTC to 2016-02-11 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-11 18:00:00 UTC to 2016-02-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-12 00:00:00 UTC to 2016-02-12 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-12 06:00:00 UTC to 2016-02-12 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-12 12:00:00 UTC to 2016-02-12 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-12 18:00:00 UTC to 2016-02-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-13 00:00:00 UTC to 2016-02-13 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 13, 00:002016-02-13 06:00:00 UTC to 2016-02-13 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-13 12:00:00 UTC to 2016-02-13 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-13 18:00:00 UTC to 2016-02-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-14 00:00:00 UTC to 2016-02-14 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-14 06:00:00 UTC to 2016-02-14 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-14 12:00:00 UTC to 2016-02-14 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-14 18:00:00 UTC to 2016-02-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-15 00:00:00 UTC to 2016-02-15 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-15 06:00:00 UTC to 2016-02-15 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-15 12:00:00 UTC to 2016-02-15 18:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 15, 12:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 10, 12:002016-02-10 12:00:00 UTC2016-02-10 18:00:00 UTC101
Feb 10, 18:002016-02-10 18:00:00 UTC2016-02-11 00:00:00 UTC000
Feb 11, 00:002016-02-11 00:00:00 UTC2016-02-11 06:00:00 UTC000
Feb 11, 06:002016-02-11 06:00:00 UTC2016-02-11 12:00:00 UTC000
Feb 11, 12:002016-02-11 12:00:00 UTC2016-02-11 18:00:00 UTC000
Feb 11, 18:002016-02-11 18:00:00 UTC2016-02-12 00:00:00 UTC000
Feb 12, 00:002016-02-12 00:00:00 UTC2016-02-12 06:00:00 UTC000
Feb 12, 06:002016-02-12 06:00:00 UTC2016-02-12 12:00:00 UTC000
Feb 12, 12:002016-02-12 12:00:00 UTC2016-02-12 18:00:00 UTC000
Feb 12, 18:002016-02-12 18:00:00 UTC2016-02-13 00:00:00 UTC000
Feb 13, 00:002016-02-13 00:00:00 UTC2016-02-13 06:00:00 UTC000
Feb 13, 06:002016-02-13 06:00:00 UTC2016-02-13 12:00:00 UTC000
Feb 13, 12:002016-02-13 12:00:00 UTC2016-02-13 18:00:00 UTC000
Feb 13, 18:002016-02-13 18:00:00 UTC2016-02-14 00:00:00 UTC000
Feb 14, 00:002016-02-14 00:00:00 UTC2016-02-14 06:00:00 UTC000
Feb 14, 06:002016-02-14 06:00:00 UTC2016-02-14 12:00:00 UTC000
Feb 14, 12:002016-02-14 12:00:00 UTC2016-02-14 18:00:00 UTC000
Feb 14, 18:002016-02-14 18:00:00 UTC2016-02-15 00:00:00 UTC000
Feb 15, 00:002016-02-15 00:00:00 UTC2016-02-15 06:00:00 UTC000
Feb 15, 06:002016-02-15 06:00:00 UTC2016-02-15 12:00:00 UTC000
Feb 15, 12:002016-02-15 12:00:00 UTC2016-02-15 18:00:00 UTC110

What Hacker News says

2 sources
I took a look at the code in the author's GitHub repository. The data sources are CSVs in this repository: https://github.com/BobAdamsEE/SouthParkData/ Looks like all the data is preprocessed, with everyone mostly having only 1 line. (Actually, it appears the line you note in 10-3 is broken!) You can make an argument that the script isn't processed correctly, but that's beyond the scope of the analysis, although a note might be helpful.
In Text Mining South Park

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.