Help:Change propagation

Jump to: navigation, search
Some insights as what requires change propagation to be successful
Table of Contents

Changes to a value annotation (respectively a page or template that contains an annotation) and its propagation depends on how its is included or annotation are made available.

Transcluded content

Content that has been transcluded using {{:myPage}} (or as template {{myTemplate|param=foo}}) into a page (including its value annotations) requires that the refreshLinks job has been run first before changed values are made available to the Semantic MediaWiki backend (and hereby possible dependant queries and its result display).

This is even more important for use cases where {{:myPage}} itself transcludes data from a template and requires updates. The job queue is expected to be scheduled appropriately to ensure updates are dispatched within a short period of time to avoid a large backlog.

Property type and/or constraint changes

Changing the type of a property or its constraints (e.g. allows values) can require a comprehensible computing effort (it largely depends on where and how often the property is being used or referenced) therefore a change is not immediately visible until the UpdateDispatcherJob has finalized its processing on all dependencies and has generated UpdateJob's for each subject that embeds the property.

Query result changes

See also