JADE/Integration

This page describes what data can be included in JADE content. It is intended for developers and integrators. It is provided by a pre-release extension, only available on the Beta Cluster until further notice.

Judgments
We currently support judgments about three types of wiki entities:


 * Diff - Any edit to a page, for example https://en.wikipedia.org/?diff=12345678
 * Revision - Snapshot of a page's content, for example https://en.wikipedia.org/wiki/Sinharaja_Forest_Reserve?oldid=12345678
 * Page - Attributes of a page which won't change as the page evolves. For example, categories or WikiProjects it might be associated with, or whether the subject is notable.

To challenge a judgment, create and endorse an alternative judgment. We have built-in assumptions loosely supporting Wikipedia's Bold-Revert-Discuss and !vote standards for building consensus. To support a judgment, you can add to the "notes" field, create another judgment with the same data, or state your opinions on the talk page.

We encourage users and integrators to offer free-text justifications or other explanations in the judgment "notes" field. This will be part of the judgment page and can be edited again later.

API
We recommend going through the API for most tasks, since it hides some of the complexities of translation and data structure. There will be two API methods supplied through MediaWiki:


 * createjudgment - Create a single judgment about an entity.

Signature:$\text{entity-type, entity-id, schema, data, [notes], [summary], [tags]} \rightarrow \text{status}$

Example (must also post a token): https://mediawiki.org/w/api.php?action=createjudgment&entitytype=diff&entityid=3&schema=damaging&data=true&notes=just%20because


 * getjudgments - Get all judgments about an entity.

Signature: $\text{entity-type, entity-id} \rightarrow \text{judgment-page}$

Example: https://mediawiki.org/w/api.php?action=query&list=getjudgments&gjentitytype=diff&gjentityid=3&format=json

Wiki, namespace, and title
Judgments are stored on the same wiki as the page being judged, in the  namespace. Permissions for this namespace should be the same as for regular content namespaces. There is also a  namespace for discussion about each JADE page.

The title must correspond to the entity being judged. For example, judgments about the edit https://en.wikipedia.org/?diff=12345678 must appear at https://en.wikipedia.org/wiki/Jade:Diff/12345678. Each type of wiki entity has its own page title structure:


 * Jade:Diff/12345678
 * Jade:Revision/12345678
 * Jade:Page/582115

Note that all page title components are translated, for example "Суждение:Версия/12345678".

Data structure
JADE pages contain a list of judgments for each schema. Judgment schemas currently follow the ORES model types, see our configuration for the defaults, under the  key.

One judgment per schema may be chosen as the  value, which represents the current consensus.

The minimum valid  judgment page:

A more interesting example, with conflicting judgments (this is fine), some notes, and both  schemas represented.

Each wiki entity type supports different schemas, see how the  judgment only supports the   article quality schema.

Page judgments aren't specific to a revision, note that we have a  but no.

Validation
JADE pages are validated before they are saved to the database, and if the data format is incorrect the edit will be aborted. Internally, we specify most of our validation rules as a JSON schema, which you can read here. You can run your own validation locally using the JSON schema libraries available for many programming languages.

Judgment content must refer to a real revision or page.

An additional validation is done on the page title, which must match the entity being judged as described above.

Detailed validation errors are generated internally, but aren't made available to frustrated users—please follow progress in https://phabricator.wikimedia.org/T197653

Bots, abuse, notability
The JADE service can only handle a small volume of judgments at the moment, so we ask that discretion is used when writing any automation against it. There is storage available for judgments, but only for a human-scale magnitude of them. Please do not create judgments for any type of "autopatrolled" predictions.

We don't have notability requirements for JADE, enjoy!