VIEWVIEWVIEW commited on
Commit
1cfc01d
·
verified ·
1 Parent(s): 636d22d

Update dataset card

Browse files
Files changed (1) hide show
  1. README.md +141 -3
README.md CHANGED
@@ -1,3 +1,141 @@
1
- ---
2
- license: mit
3
- ---
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ pretty_name: pr0gramm user comments
3
+ license: other
4
+ task_categories:
5
+ - text-mining
6
+ language:
7
+ - de
8
+ - en
9
+ size_categories:
10
+ - 10M<n<100M
11
+ ---
12
+
13
+ # pr0gramm-usercomments
14
+
15
+ This dataset contains a SQLite database of pr0gramm item metadata and item comments.
16
+
17
+ Current file in the repo:
18
+
19
+ - `pr0gramm.sqlite3`
20
+
21
+ ## Coverage
22
+
23
+ From the current database snapshot, comments are present up to item `6986879`.
24
+
25
+ The newest item rows currently in `items` are:
26
+
27
+ - `6986879` created at `2026-04-17 19:17:36 UTC`
28
+ - `6986878` created at `2026-04-17 19:17:30 UTC`
29
+ - `6986877` created at `2026-04-17 19:16:19 UTC`
30
+
31
+ The latest observed detail crawl time for those rows is `2026-04-17 19:18:03 UTC`.
32
+
33
+ This means the uploaded snapshot includes comment coverage at least through that item range. Not every nearby item necessarily has comments, because many items on pr0gramm simply have zero comments.
34
+
35
+ ## Database layout
36
+
37
+ The SQLite file contains these tables:
38
+
39
+ - `comments`
40
+ - `items`
41
+ - `crawl_state`
42
+ - `item_detail_failures`
43
+
44
+ ### `comments`
45
+
46
+ One row per comment.
47
+
48
+ Columns:
49
+
50
+ - `comment_id` INTEGER PRIMARY KEY
51
+ - `item_id` INTEGER NOT NULL
52
+ - `parent_comment_id` INTEGER
53
+ - `comment_time` INTEGER
54
+ - `score` INTEGER
55
+ - `upvotes` INTEGER
56
+ - `downvotes` INTEGER
57
+ - `crawl_time` INTEGER NOT NULL
58
+ - `user_name` TEXT
59
+ - `user_id` INTEGER
60
+ - `user_profile_url` TEXT
61
+ - `body` TEXT
62
+ - `raw_json` TEXT NOT NULL
63
+
64
+ ### `items`
65
+
66
+ One row per crawled item.
67
+
68
+ Columns:
69
+
70
+ - `item_id` INTEGER PRIMARY KEY
71
+ - `promoted` INTEGER
72
+ - `flags` INTEGER
73
+ - `created_at` INTEGER
74
+ - `user_name` TEXT
75
+ - `source_feed` TEXT NOT NULL
76
+ - `crawl_time` INTEGER NOT NULL
77
+ - `raw_json` TEXT NOT NULL
78
+ - `detail_crawl_time` INTEGER
79
+
80
+ ### `crawl_state`
81
+
82
+ Crawler checkpoint state.
83
+
84
+ Columns:
85
+
86
+ - `key` TEXT PRIMARY KEY
87
+ - `value` TEXT NOT NULL
88
+ - `updated_at` INTEGER NOT NULL
89
+
90
+ ### `item_detail_failures`
91
+
92
+ Tracks item detail fetch failures.
93
+
94
+ Columns:
95
+
96
+ - `item_id` INTEGER PRIMARY KEY
97
+ - `first_failed_at` INTEGER NOT NULL
98
+ - `last_failed_at` INTEGER NOT NULL
99
+ - `attempt_count` INTEGER NOT NULL
100
+ - `last_error` TEXT NOT NULL
101
+ - `terminal` INTEGER NOT NULL DEFAULT 0
102
+ - `resolved_at` INTEGER
103
+
104
+ ## Notes
105
+
106
+ - Unix timestamps are stored as integer seconds.
107
+ - `raw_json` keeps the original API payload for reproducibility.
108
+ - The database may contain items without comments.
109
+ - The database may also contain unresolved detail failures for some items that need a later retry.
110
+
111
+ ## Example queries
112
+
113
+ Show the latest item with at least one stored comment:
114
+
115
+ ```sql
116
+ SELECT item_id
117
+ FROM comments
118
+ ORDER BY item_id DESC
119
+ LIMIT 1;
120
+ ```
121
+
122
+ Show recent commented items:
123
+
124
+ ```sql
125
+ SELECT item_id, COUNT(*) AS comments
126
+ FROM comments
127
+ GROUP BY item_id
128
+ ORDER BY item_id DESC
129
+ LIMIT 20;
130
+ ```
131
+
132
+ Inspect the newest crawled items:
133
+
134
+ ```sql
135
+ SELECT item_id,
136
+ datetime(created_at, 'unixepoch') AS created_at_utc,
137
+ datetime(detail_crawl_time, 'unixepoch') AS detail_crawl_time_utc
138
+ FROM items
139
+ ORDER BY item_id DESC
140
+ LIMIT 20;
141
+ ```