Change Details

We're considering several JADE integrations which will happen in the MediaWiki extension layer. In this design, workflows such as patrolling, FlaggedRevs, and PageTriage would hook into JADE and cause judgments to be created or updated. Define and implement this API and attempt an integration to validate. Requirements: * Create a judgment from (entity, schema, judgment content, notes, user identity). * Update a judgment. Probably pass a lastRevId for conflict resolution. * Do these CRUD actions in a background job. * Won't require any changes to the external workflows, we can incrementally enrich the data with things like free-form text notes. Draft: https://etherpad.wikimedia.org/p/JADE_API

We're considering several JADE integrations which will happen in the MediaWiki extension layer. In this design, workflows such as patrolling, FlaggedRevs, and PageTriage would hook into JADE and cause judgments to be created or updated. Define and implement this API and attempt an integration to validate. Requirements: * [x] Create a judgment from (entity, schema, judgment content, notes, user identity). * [x] Won't require any changes to the external workflows, we can incrementally enrich the data with optional data such as free-form text notes. * [x] Clients can fetch a judgment given (entity_type, entity_id). Declined requirements: * Update a judgment. Probably pass a lastRevId and section ID for conflict resolution. * Make the create action available in a background job. Draft: https://etherpad.wikimedia.org/p/JADE_API

We're considering several JADE integrations which will happen in the MediaWiki extension layer. In this design, workflows such as patrolling, FlaggedRevs, and PageTriage would hook into JADE and cause judgments to be created or updated. Define and implement this API and attempt an integration to validate. Requirements: * [x] Create a judgment from (entity, schema, judgment content, notes, user identity). * Update a judgment. Probably pass a lastRevId for conflict resolution[x] Won't require any changes to the external workflows, we can incrementally enrich the data with optional data such as free-form text notes. * Do these CRUD actions in a background job[x] Clients can fetch a judgment given (entity_type, entity_id). Declined requirements: * Update a judgment. Probably pass a lastRevId and section ID for conflict resolution. * Won't require any changes to* Make the external workflows, we can incrementally enrich the data with things like free-form text notescreate action available in a background job. Draft: https://etherpad.wikimedia.org/p/JADE_API