The following graph gives an overview of the editing pipeline:
- The schema is evaluated (
WikibaseSchema::evaluate) on each visible row in the project. This gives rise to one or more
EntityEditobjects for each row. Those objects represent a candidate edit, including the configuration of how this edit should be matched to any existing data on the entity to be edited.
WikibaseAPISchedulergroups the edits together, so that they can later be performed with the HTTP Wikibase API efficiently. This essentially means bundling up all changes made to the same entity across the project into a single object. If new edits are made, those edits also need to be ordered so that any new entity referenced in an edit already exists by the time this edit is made.
- A collection of
EditScrutinizers are executed on the candidate edits, to check for detectable issues about those. This generate
QAWarningobjects which are aggregated according to keys defined by the scrutinizers. This collection of scrutinizers is largely based on the constraint system offered by WikibaseQualityConstraints, when it is used by the target Wikibase.
The steps above are executed every time the schema is previewed. When the user is ready to upload their edits to Wikibase, they have a choice between two routes:
- Going through QuickStatements. The
QuickStatementsScheduleroffers another way to group edits together, such that they can be expressed in the QuickStatements v1 format. The
QuickStatementsExportertranslates them to that format.
They can also upload their edits directly from OpenRefine, in which case the following operations are executed for each edit:
- The edit is rewritten, so that if it references any newly created Wikibase entity, the identifier of this entity is inserted in the edit. This is done by
- For edits to existing entities, the edit is compared to any existing data on the item. Following the matching criteria stored in the edit, we generate a concrete update of entity data. This is done by
- Finally, the update is sent to the Wikibase instance using Wikidata-Toolkit.