What Makes Sports Fans Interactive? Identifying Factors Affecting Chat Interactions in Online Sports Viewing

1. Chat message data - kbo2011_naverbasevall_comment.sql: chat messages in Naver Sports that users posted in 2011 - kbo2012_naverbasevall_comment.sql: chat messages in Naver Sports that users posted in 2012 Each MySQL table consists of the following six columns. 1. comment_id: Integer variable to identify each comment 2. gid: Integer variable to identify each game 3. uid: Integer variable to identify each user 4. category_id: A team name that a user selected when a chat message is posted 5. content: Chat message text 6. post_time_relative: Elapsed seconds since the game starts 2. KBO game information - game_basic.sql: KBO game information in 2011/2012 (This data was collected from here, http://sports.news.naver.com/schedule/index.nhn?uCategory=&category=kbo&year=2010&month=03) This MySQL table consists of the following 12 columns. 1. gid: Integer variable to identify each game 2. game: Game ID used in Naver Sports 3. year: year of the game play 4. month: month of the game play 5. date: date of the game play 6. time: time of the game play 7. day: day of the game play 8. team_away: name of the away team 9 team_home: name of the home team 10. score_away: score by the away team 11. score_home: score by the home team 12. location: location of the game play 3. KBO game play-by-play data - game_playbyplay.sql: playbyplay data in 2011/2012 (This data was collected from Naver Sports; EX, http://sports.news.naver.com/gameCenter/gameRecord.nhn?category=kbo&gameId=20100327HHSK0) This MySQL table consists of the following 21 columns. 1. play_no: Integer variable to identify each play 2. gid: Integer variable to identify each game 3. inning: inning of the play 4. pitcher: current pitcher name 5. batter: current batter name 6. batter_no: current batter order 7. pitch: the pitch result 8. strike: current number of strikes 9. ball: current number of balls 10. out_cnt: current number of outs 11. score_home: current score of the home team 12. score_away: current score of the away team 13. 1st_base: player name on the 1st base 14. 2nd_base: player name on the 2nd base 15. 3rd_base: player name on the 3rd base 16. runner_state: overall state of the three bases (ex: 1 --> A player is on 1st base, but 2nd and 3rd bases are empty, 13 --> Two players are on 1st and 3rd bases respectively, but 2nd base is empty) 17. runner_cnt: the number of players on bases 18. result_r: r by this play 19. result_rbi: rbi by this play 20. result_score_home: total home score after this play 21. result_score_away: total away score after this play 4. Winning rate data - game_winrate.sql: winning rates of the home/away teams for an inning (This data is calculated based on the playbyplay data. For the details, please refer to our paper--currently under review) This MySQL table consists of the following 21 columns. 1. play_no: Integer variable to identify each play 2. gid: Integer variable to identify each game 3. inning: inning of the play 4. away_win: probability that the away team will win this game 5. draw: probability that the game will finish a tie 6. home_win: probability that the home team will win this game If you have any question about the dataset, please contact Minsam Ko ([e-mail]).

1. 聊天消息数据：对应两个SQL脚本文件，分别为`kbo2011_naverbasevall_comment.sql`与`kbo2012_naverbasevall_comment.sql`，包含2011年与2012年用户在Naver体育（Naver Sports）平台发布的赛事聊天消息。每张MySQL数据表均包含以下6个字段：
1. `comment_id`：用于标识单条评论的整型变量
2. `gid`：用于标识单场赛事的整型变量
3. `uid`：用于标识单个用户的整型变量
4. `category_id`：用户发布聊天消息时选定的支持球队名称
5. `content`：聊天消息文本内容
6. `post_time_relative`：自赛事开赛以来的累计秒数
2. 韩国职业棒球联盟（Korea Baseball Organization，简称KBO）赛事基础信息：`game_basic.sql`，包含2011/2012赛季的KBO赛事基础信息（数据采集自链接：http://sports.news.naver.com/schedule/index.nhn?uCategory=&category=kbo&year=2010&month=03）。该MySQL数据表包含以下12个字段：
1. `gid`：用于标识单场赛事的整型变量
2. `game`：Naver体育平台使用的赛事专属ID
3. `year`：赛事举办年份
4. `month`：赛事举办月份
5. `date`：赛事举办日期
6. `time`：赛事举办时间
7. `day`：赛事举办当日的星期标识
8. `team_away`：客场球队名称
9. `team_home`：主场球队名称
10. `score_away`：客场球队单场得分
11. `score_home`：主场球队单场得分
12. `location`：赛事举办场地
3. KBO赛事逐回合攻防数据：`game_playbyplay.sql`，包含2011/2012赛季的赛事逐回合攻防记录（数据采集自Naver体育平台，示例链接：http://sports.news.naver.com/gameCenter/gameRecord.nhn?category=kbo&gameId=20100327HHSK0）。该MySQL数据表包含以下21个字段：
1. `play_no`：用于标识单次攻防回合的整型变量
2. `gid`：用于标识单场赛事的整型变量
3. `inning`：攻防回合所属局数
4. `pitcher`：当前登场投手姓名
5. `batter`：当前登场打者姓名
6. `batter_no`：当前打者的击球顺序号
7. `pitch`：投球结果详情
8. `strike`：当前累计好球数
9. `ball`：当前累计坏球数
10. `out_cnt`：当前累计出局数
11. `score_home`：当前主场球队实时得分
12. `score_away`：当前客场球队实时得分
13. `1st_base`：占据一垒的跑垒员姓名
14. `2nd_base`：占据二垒的跑垒员姓名
15. `3rd_base`：占据三垒的跑垒员姓名
16. `runner_state`：三垒垒包的整体占位状态（示例：`1`表示仅一垒有跑垒员，二、三垒无人；`13`表示一垒与三垒各有一名跑垒员，二垒无人）
17. `runner_cnt`：垒上总跑垒员人数
18. `result_r`：本次攻防产生的得分（Run）
19. `result_rbi`：本次攻防产生的打点（Run Batted In）
20. `result_score_home`：本次攻防结束后主场球队的总得分
21. `result_score_away`：本次攻防结束后客场球队的总得分
4. 胜率数据：`game_winrate.sql`，包含单局下主客场球队的赛事获胜概率（该数据基于逐回合赛事数据计算所得，详细说明请参阅我们目前处于同行评审阶段的学术论文）。该MySQL数据表包含以下字段：
1. `play_no`：用于标识单次攻防回合的整型变量
2. `gid`：用于标识单场赛事的整型变量
3. `inning`：攻防回合所属局数
4. `away_win`：客场球队最终获胜的概率
5. `draw`：赛事最终平局的概率
6. `home_win`：主场球队最终获胜的概率

若您对该数据集有任何疑问，请联系Minsam Ko（邮箱：[e-mail]）。