Baloo/Schema

The Blackhole database contains two tables: the contributions, and the entrypoints.

Contributions

All contribution data follows this schema:

• guid: Globally Unique Identifier of the contribution (string)
• email: email address of contributor (string)
• datetime: date and time of contribution (datetime)
• canonical: permanent URL to contribution (string)
• volunteer: boolean value indicating paid employee status (boolean)
• type: a codified string that describes the contribution (string)
• source: source of contribution, one of the following: (string)
  • bugzilla
  • hg
  • sumo
• extra: per-contribution data, following a source-dependent schema (dictionary)

extra - Bugzilla

• fields: fields modified (list of string)
• values: values of modified fields, where available. Keys correspond to names of modified fields. (dictionary)
• id: bug id (integer)
• product: product (string)
• component: component (string)
• new: new bug creation (boolean, optional)
• firstpatch: first patch flag (boolean, optional [likely doesn't work])
• comment: associated comment ID (integer, optional)
• review: review flag was modified (set, cleared, changed, etc) (boolean, optional)
• feedback: feedback flag was modified (set, cleared, changed, etc) (boolean, optional)
• needinfo: needinfo flag was modified (set, cleared, changed, etc) (boolean, optional)

extra - hg

• tree: tree name (eg. mozilla-central) (string)
• sha: revision hash (string, doesn't exist yet)

extra - sumo

• type: type of SUMO contribution, one of: (string)
  • answer
  • post
  • discuss
  • revision
• locale: locale of contribution (string)

extra - sumo - answer

• question: id of answered question (integer)
• id: id of answer (integer)
• product: associated product slug (string)
• topic: associated topic slug (string)

extra - sumo - post

• thread: id of associated forum thread (integer)
• id: id of post (integer)
• slug: associated forum slug (string)

extra - sumo - discuss

• article: id of associated article (integer)
• thread: id of associated discussion thread (integer)
• id: id of post (integer)
• new: new post, or edit of existing (boolean)
• slug: associated article slug (string)

extra - sumo - revision

• article: id of associated article (integer)
• revision: id of revision (integer)

extra - reps (planned)

• report-date: when the contribution was reported (datetime)
• report-type: type of report (string)
• campaign: campaign that the contribution supports (string)
• contribution-areas: contribution areas that are supported by this contribution (string)
• location: location (latitude, longitude?)
• extra: additional text about the contribution (string)
• url: canonical URL for the activity (string)

Entrypoints

Data representing first contact points for potential contributors. These may not actually be first contact, but the are places where first contact often occurs.

All entrypoint data follows this schema:

• email: email address of contactee (string)
• datetime: date and time of contact (datetime)
• canonical: permanent URL to point of contact (string)
• source: source of contact, one of the following: (string)
  • contribute
  • sumo
• extra: per-entrypoint data, following a source-dependent schema (dictionary)

extra - contribute

• interest: category selected for interest (eg. Coding, Web Development, etc.) (string)

extra - sumo

• id: id of new question (integer)
• product: name of product (string)
• category: name of category (string)