Wikilabels allows users to generate structured data for random samples of edits. Maybe Wikilabels can manage campaigns and worksets while JADE stores all labels.
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Invalid | None | T148700 JADE: UI/API for reviewing/refuting how ORES classifies you and your stuff | |||
Declined | None | T153150 [Discuss] Could Wiki Labels backend be replaced with JADE? |
Event Timeline
We're looking at similar integrations with patrolling, PageTriage, and FlaggedRevs. Wiki labels should fit into this pattern nicely.
I'd like to humbly propose bumping up the priority for this.
To the extent JADE is meant to be a back-end integrated into other applications, Wiki Labels is conveniently available as our test case for such an integration. It may also be easier to convince other developers to join in once we have a working integration to show off. It's probably also easier to integrate our own product into JADE as an initial case than a third party tool. Finally, it helps with the long-term maintainability of Wiki Labels.
Please let me know what you think.
As JADE develops it is moving closer to a model where multiple people can collaborate on a single judgment for a given entity. This goes against the requirements that Wikilabels (a) allow different people to make multiple judgments on the same entity and (b) treat judgments as immutable actions. As such, it makes sense to recognize JADE and Wikilabels as separate products with separate purposes.