From mediawiki.org
(Redirected from JADE/Integration)
Jump to navigation Jump to search
Warning Warning: JADE is no longer in active development. See Topic:W94jqvwnqgagqowz.
MediaWiki extensions manual
OOjs UI icon advanced.svg
Release status: beta
Implementation API , ContentHandler , User interface, Database
Description Robust false-positive and feedback gathering system, to allow human refutation and review of ORES scoring.
Author(s) The Scoring Platform team
Latest version continuous updates
MediaWiki 1.35+
PHP 7.2+
MediaWiki 1.36 Not formally tested
MediaWiki 1.34 Not formally tested
MediaWiki 1.32 Not formally tested
Composer 1.9.0
License GNU General Public License 3.0 or later
  • $wgJadeContentQualityLevels
  • $wgJadeAllowedFacets
  • $wgJadeEntityTypeNames
  • $wgJadeAllowedScoringSchemas
Translate the Jade extension if it is available at translatewiki.net

Check usage and version matrix.

Vagrant role jade
Issues Open tasks · Report a bug

The Jade (Judgment And Dialog Engine) extension provides two new namespaces, Jade and Jade_talk, used for collecting and discussing labels. Labels (also known as Proposals) are an opinion about a wiki revision, diff, or page.

For background information, see the Jade project page.


  • Download and place the file(s) in a directory called Jade in your extensions/ folder.
  • Only when installing from git run Composer to install PHP dependencies, by issuing composer install --no-dev in the extension directory. (See task T173141 for potential complications.)
  • Add the following code at the bottom of your LocalSettings.php:
    wfLoadExtension( 'Jade' );
  • Yes Done – Navigate to Special:Version on your wiki to verify that the extension is successfully installed.


// Provide proposal title translations for your wiki.
$wgJadeEntityTypeNames = [
'diff' => 'Разница',
'revision' => 'Версия',
'page' => 'Страница',

// For Wikidata: replace the wp10 article quality scale with something wacky.
$wgJadeAllowedScoringSchemas['revision'] = [ 'itemquality' ];


To add interface support for your language, please help translate at https://translatewiki.net/wiki/Special:MessageGroupStats?group=ext-jade


Pages in the Jade namespace have the following title specifications: Jade:<type>/<id>. For example, if we wanted to label a a specific edit for revision id 123, then we would navigate to the page Jade:Diff/123.


1. Propose and endorse a new label Users can propose a label for a given facet on any Jade page. For example, if you wanted to propose a label about 'editquality', then you would click the 'Propose New Label' button under the 'editquality' section, select a label, add notes and publish your proposal. Note that this will also add your endorsement to the newly proposed label. To challenge a proposal, create and endorse an alternative proposal.

2. Endorse an existing label To endorse a proposal, you can post a signed comment to its endorsement section or create another proposal with supporting data and your own comments.

3. Promote a label as consensus Users can promote a 'preferred' label as consensus by selecting 'Promote' from the Label drop-down menu.

4. Edit label notes and endorsement comments We encourage users and integrators to offer free-text justifications or other explanations in the proposal notes field. These notes are stored publicly as part of the Jade entity page and can be edited later. You can edit a label's notes by selecting the 'Edit' option in the label's drop-down menu. Similarly, you can edit your own endorsement comment by selecting 'Edit' in your endorsement's drop-down menu.

5. Move an Endorsement You can move an endorsement from one label to another by selecting 'Move' from the endorsement's drop-down menu.

6. Delete Labels and Endorsements Users can delete a label or endorsement from the label or endorsement drop-down menus.

All of these mechanisms should support both Wikipedia's Bold-Revert-Discuss and !vote standards for building consensus, as needed.

Bots, abuse, and quality standards[edit]

Please do not create proposals for "autopatrolled" predictions, nor any automatically or semi-automatically generated data. This includes scores from ORES unless you have verified, using your own judgment, that the correct score is the same score given by ORES.

We ask that developers don't integrate without including the collaboration features. For example, don't send a "damaging: true" proposal as a side-effect of a patrolling workflow, unless the interface also shows existing proposals, the proposal notes, links to the entity page and so on.

Beyond these requirements, nothing is non-notable in Jade. Enjoy!

Secondary Integrations[edit]

Jade Entity data structure[edit]