JADE/Implementation

Technical notes, in need of organization and linking.


 * Imagine the widest range of use cases.


 * Identifies human evaluators through wiki account


 * Could become the backend or a replacement for wikilabels: people making collective judgment calls about commits, reverts, and admin actions will give us the same data points as WikiLabels does today.


 * Abuse curation
 * Should probably plug into AbuseFilter.
 * We can borrow from MediaWiki's global user rights (ORES is global) for curation privs.


 * UI
 * Where would we put the proof-of-concept refutation UI?   This might involve an overlay on MediaWiki or a stand-alone system.  Could be a plugin to ORES dashboards.
 * Imagining recent changes-like dashboard for judgements.
 * Surface entrypoint to provide feedback anywhere that a revscore appears.
 * Try to identify potentially problematic scores and flag them for review or refutation.


 * API
 * Query for past judgements
 * Apply new judgements
 * Review recent judgements and suppress problematic judgement comments.
 * Schema
 * Please don't reinvent the wheel. Store your data in actual pages (or in Special:Log) and everything will come for free.
 * Indexed for easy join with ORES scores.
 * We could probably use triples of (, , ).  E.g. ("enwiki", "revision", 2345671)
 * have a table like you suggest, and "target entity" is just a row in this table
 * Potentially store in Wikibase.