pcomments Table

Overview

Each row in this table represents a comment left on a project. This table includes all comments that were publicly visible on every project page in the Scratch website at the time of composing this dataset.

This table contains the metadata for these comments and includes who, when, and on which project each comment was posted.

Any user who was logged in could post comments on projects although project creators could manually disable comments on a project-by-project basis. Comments were threaded in the sense that the website graphically reflected when comments were replies to other comments. Individual comments could be deleted by the creator of a project, by administrators, or might be automatically censored.

The text or content of the comment is in the pcomments_text textual table.

Description of Fields

The final includes 7,788,414 observations. Each observation corresponds to a single comment.

Variable Type Description
pcomment_id integer Unique identifier for each row in the project comments table. Used internally for every recorded comment as well as being displayed in URLs and links. This field is "autoincremented" and increases monotonically over time.
project_id integer Unique identifier for the project that is the target of the comment , i.e., the project being commented on (see the projects table).
user_id integer Unique identifier of the user who left this comment on the project (see the users table).
date_created datetime The date that the comment was left.
reply_to_pcomment_id integer The unique identifier of the comment that was replied to. This is set to missing/NA if the comment is not a reply and takes a value corresponding to another 'pcomment_id' value otherwise.

Summary Statistics

plot of chunk unnamed-chunk-2

Omitted Observations

In the MySQL database, there is a comment_visibility field which includes the visibility status of comments as one of several options. Only comments marked as visible are included in this table. In the database, there is the following distribution of values for this field:

Status Count
EMPTY 1
censbyadmin 23393
censbycomm 7705
delbyadmin 59201
delbyparentcomment 64972
delbyusr 128558
hiddenduetourl 2462
parentcommentcensored 18272
visible 9713878

There is a second Boolean field, visibility that almost always matches the comment_visibility field. Because it is the conservative course, we omit the 96 comments that are marked as visible in the comment_visibility field but marked as FALSE in the visibility field.

Additionally, we remove comments made by users whose profiles are not public or that are left on projects that are not public. The distribution of projects across these two possibility is shown in following cross tabulation:

Users Exists Project Exists Count
FALSE FALSE 25618
TRUE FALSE 1895458
FALSE TRUE 4292
TRUE TRUE 7788414

We retain only the 7,788,414 that include all comments where both the user and project exists in our database.

Download Datasets

These data are access restricted. Details on gaining access are provided in the "Permission to Use Datasets" section of the overview page.