JADE/Implementations

This page describes a set of thoughts about implementations of JADE that correspond to a set of use-cases. See T166053 for the tracking task.

System overview

 * REST HTTP API
 * Accessible from a public address
 * Allows all relevant operations (save/update judgement, suppress comment, etc.)
 * Integrates with MediaWiki authentication
 * Queryable in some basic ways (e.g. give me all judgement for an artifact)
 * ORES integration
 * Provides fast access to judgements to integrate with ORES predictions (ORES response time for cached scores is ~50ms. We shouldn't be slower than 100ms)
 * Some concept of overlap between ORES models/scores and JADE artifacts
 * Public query-ability
 * Users are able to run SQL (or similarly easy query language) that joins judgements with production database tables.
 * Curation activities
 * A feed/stream of recent judgments for curation work
 * Users will be able to suppress comments and usernames that are offensive or violate privacy.

Auditing

 * Reporting problems
 * Grounded theory
 * Effective refutation of predictions
 * Showing improvements

Label storage

 * Judgments are labels
 * Improve labels by directing attention to borderline cases